From: Paul Mundt <lethal@linux-sh.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: 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 19:44:47 +0900 [thread overview]
Message-ID: <20090112104447.GG28564@linux-sh.org> (raw)
In-Reply-To: <48E9AE16.2000002@snapgear.com>
On Mon, Oct 06, 2008 at 04:20:06PM +1000, Greg Ungerer wrote:
> Hi Kosako,
>
> KOSAKI Motohiro wrote:
> >I guess nobody don't test m68knommu at all last three month.
> >Do we still need to maintain this architecture?
>
> Yes, we do.
>
Any effort to get m68knommu folded in to m68k proper? This might help
with some of your bitrot issues.. And likely less work to do in
supporting those m68knommu parts that ship with MMUs ;-)
m68knommu is the only one of the mmu/nommu variants left that ships in
its own architecture directory rather than being folded in to its parent.
It would be good to get rid of it one of these days.
next prev parent reply other threads:[~2009-01-12 10:44 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 [this message]
2009-01-12 10:59 ` Sam Ravnborg
[not found] ` <20090112105942.GA10936@uranus.ravnborg.org>
2009-01-12 11:07 ` Ingo Molnar
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=20090112104447.GG28564@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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