All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Thomas Gleixner <tglx@linutronix.de>
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: Tue, 22 Feb 2011 12:05:20 +1000	[thread overview]
Message-ID: <4D6319E0.9080907@snapgear.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1102212216540.2701@localhost6.localdomain6>

Hi Thomas,

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 ?

I'll look at doing what I can as I work through merging all the
underlying pieces :-)

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  reply	other threads:[~2011-02-22  2:05 UTC|newest]

Thread overview: 25+ 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  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 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-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-03-18  7:24                 ` Geert Uytterhoeven
2011-02-21 21:18 ` Thomas Gleixner
2011-02-22  2:05   ` Greg Ungerer [this message]
2011-02-22  7:14     ` Geert Uytterhoeven
2011-02-22  7:29       ` Sam Ravnborg
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=4D6319E0.9080907@snapgear.com \
    --to=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=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.