Messages in this thread | | | Date | Tue, 22 Feb 2011 08:14:08 +0100 | Subject | Re: merge of m68knommu and m68k arch branches? | From | Geert Uytterhoeven <> |
| |
On Tue, Feb 22, 2011 at 03:05, Greg Ungerer <gerg@snapgear.com> wrote: > On 22/02/11 07:18, Thomas Gleixner wrote: >> On Fri, 18 Feb 2011, Greg Ungerer wrote: >>> Inside of the new arch/m68k is a little messy in the kernel and mm >>> directories. There is plenty of scope for cleanup and merge on the >>> files in here - but I want to leave that for follow up patches after >>> this initial directory merge. As a data point, when we merged the >>> m68k and m68knommu include files we had something like 70 or 80 >>> duplicate but separate files, after some cleanups that is now down to >>> 10. Ongoing cleanup will merge some of these remaining ones as well. >>> >>> Thoughts? >> >> Hmm, how are you going to deal with the fact, that m68knommu uses >> genirq, m68k not? I guess there are some more points like this >> (clockevents, clocksource ...) > > Initially it has no impact. This first step pretty much just > combines the 2 directories, it doesn't attempt to do a fine > grained merge of each file. (It does factor out identical > files - quite a few in arch/m68k/lib for example). > > >> Is there a plan to move m68k to the generic facilities as well ?
Moving m68k to genirq is (the next thing?) on my list...
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |