From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@snapgear.com>,
Thomas Gleixner <tglx@linutronix.de>,
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 09:04:46 +0100 [thread overview]
Message-ID: <20110222080446.GA25012@merkur.ravnborg.org> (raw)
In-Reply-To: <AANLkTi=o9hQM1DqbBOAsDpxBW9U1uHsUZ6q3Kw48OBb6@mail.gmail.com>
On Tue, Feb 22, 2011 at 08:40:53AM +0100, Geert Uytterhoeven wrote:
> On Tue, Feb 22, 2011 at 08:29, Sam Ravnborg <sam@ravnborg.org> wrote:
> >> >> Is there a plan to move m68k to the generic facilities as well ?
> >>
> >> Moving m68k to genirq is (the next thing?) on my list...
> >
> > If I succeed migrating sparc32 to genirq I hope to be of a little help here.
> > It looks like a bigger task to migrate m68k than it was/is to migrate sparc32.
> >
> > It would be _very_ nice to get the last two architectures migrated to genirq.
>
> Aren't your forgetting s390?
Hmm, I had the understanding that m68k and sparc32 was the only two remaining :-(
But I did not check.
s390 sees more active maintenance so if they become the last non genirq user,
then they may feel a bit of pressure :-)
Sam
next prev parent reply other threads:[~2011-02-22 8:04 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
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 [this message]
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=20110222080446.GA25012@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=geert@linux-m68k.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox