From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
Greg Ungerer <gerg@snapgear.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"David S. Miller" <davem@davemloft.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
Greg Ungerer <gerg@uclinux.org>,
linux-m68k@lists.linux-m68k.org, stable@kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for 2.6.28 stable] m68knommu: fix m68knommu defconfig can't build
Date: Mon, 12 Jan 2009 12:07:39 +0100 [thread overview]
Message-ID: <20090112110739.GA17514@elte.hu> (raw)
In-Reply-To: <20090112105942.GA10936@uranus.ravnborg.org>
* Sam Ravnborg <sam@ravnborg.org> wrote:
> We just did the exercise with sparc/sparc64 unification and if you
> forget the few times I broke sparc32 then it went well with only limited
> problems.
We also had the x86 unification finished in the past year which went very
well too, so i can only encourage similar efforts.
> One key factor why it went well was that patches were reviewed and
> applied within a few days whch is why I stresses that the maintainer
> needs spare time to support the effort.
Yes.
Unification is the Linux meme of the century i guess ;-)
There's two main unification themes:
- per arch unification (x86, powerpc, sparc
- cross-arch unification: the moving of useful stuff out of architectures
into the core kernel (genirq, gtod, etc.).
Ingo
next prev parent reply other threads:[~2009-01-12 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 10:44 [PATCH for 2.6.28 stable] m68knommu: fix m68knommu defconfig can't build KOSAKI Motohiro
2008-10-06 6:20 ` Greg Ungerer
2009-01-12 10:35 ` KOSAKI Motohiro
2009-01-12 10:44 ` Paul Mundt
2009-01-12 10:59 ` Sam Ravnborg
[not found] ` <20090112105942.GA10936@uranus.ravnborg.org>
2009-01-12 11:07 ` Ingo Molnar [this message]
2009-01-12 11:12 ` Paul Mundt
2009-01-12 13:06 ` Greg Ungerer
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=20090112110739.GA17514@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sam@ravnborg.org \
--cc=stable@kernel.org \
--cc=zippel@linux-m68k.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