From: Thomas Gleixner <tglx@linutronix.de>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Steven King <sfking00@yahoo.com>,
uClinux development list <uclinux-dev@uclinux.org>,
Greg Ungerer <gerg@uclinux.org>,
Greg Ungerer <gregungerer@westnet.com.au>
Subject: Re: merge of m68knommu and m68k arch branches?
Date: Mon, 21 Feb 2011 22:18:42 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1102212216540.2701@localhost6.localdomain6> (raw)
In-Reply-To: <4D5DB83D.80205@snapgear.com>
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 ...)
Is there a plan to move m68k to the generic facilities as well ?
Thanks,
tglx
next prev parent reply other threads:[~2011-02-21 21:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 0:07 merge of m68knommu and m68k arch branches? Greg Ungerer
2011-02-18 7:44 ` Sam Ravnborg
2011-02-18 12:01 ` Greg Ungerer
2011-02-21 21:43 ` Arnd Bergmann
2011-02-21 21:57 ` Sam Ravnborg
2011-02-18 11:27 ` Geert Uytterhoeven
2011-02-18 15:24 ` Geert Uytterhoeven
2011-02-18 22:12 ` Greg Ungerer
2011-02-19 8:39 ` Geert Uytterhoeven
2011-02-20 23:53 ` Greg Ungerer
2011-02-21 7:41 ` Geert Uytterhoeven
2011-03-17 23:59 ` Greg Ungerer
2011-03-18 7:24 ` Geert Uytterhoeven
2011-02-21 21:18 ` Thomas Gleixner [this message]
2011-02-22 2:05 ` Greg Ungerer
2011-02-22 7:14 ` Geert Uytterhoeven
2011-02-22 7:29 ` Sam Ravnborg
2011-02-22 7:40 ` Geert Uytterhoeven
2011-02-22 8:04 ` Sam Ravnborg
2011-02-22 9:16 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1102212216540.2701@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=gregungerer@westnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking00@yahoo.com \
--cc=uclinux-dev@uclinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox