m68k: Any plans to move over to arch/m68k/include?
Almost all other architectures has moved over to arch/$ARCH/include
Are you planning to do so for m68k for next merge window?
Remaining ones: frv, h8300, m32r, m68k and mn10300
The other are done or have patches queued for next merge window to do so.
Can I be of any help?
Sam
Quoted 3 lines · Sam Ravnborg
Almost all other architectures has moved over to
arch/$ARCH/includeAre you planning to do so for m68k for next merge window?
So far _I_ don't have those plans.
Quoted 4 lines
Remaining ones: frv, h8300, m32r, m68k and mn10300
The other are done or have patches queued for next merge window to do so.Can I be of any help?
However, m68k keeps working fine after `mv include/asm-m68k arch/m68k/include/asm'. The problem is m68knommu, which includes header files from m68k. The m68k and m68knommu headers have to be merged first, cfr. Arnd Bergmann's comments and suggestions on linux-arch a while ago.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 10 lines · Geert Uytterhoeven
Quoted 3 lines · Sam Ravnborg
Almost all other architectures has moved over to
arch/$ARCH/includeAre you planning to do so for m68k for next merge window?
So far _I_ don't have those plans.
Quoted 3 lines
Remaining ones: frv, h8300, m32r, m68k and mn10300
The other are done or have patches queued for next merge window to do so.
Quoted 6 lines
Quoted 1 line
Can I be of any help?
However, m68k keeps working fine after `mv
include/asm-m68karch/m68k/include/asm'. The problem is m68knommu, which includes header files from m68k. The m68k and m68knommu headers have to be merged first, cfr. Arnd Bergmann's comments and suggestions on linux-arch a while ago.
This one (and the thread following it)
http://marc.info/?l=linux-arch&m=121753383713553&w=2
I agree this is the correct approach.
Looks reasonable simple to do for anyone having the relevant toolchains and assuming only few pending patches in this area.
I do not have time to do it for now :-(
Sam