From: Christoph Hellwig <hch@infradead.org>
To: Miles Bader <miles@gnu.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: generic hardirq code in 2.6.10-rc1
Date: Mon, 25 Oct 2004 13:36:24 +0100 [thread overview]
Message-ID: <20041025123624.GA32463@infradead.org> (raw)
In-Reply-To: <buod5z7jpws.fsf@mctpc71.ucom.lsi.nec.co.jp>
On Mon, Oct 25, 2004 at 03:02:59PM +0900, Miles Bader wrote:
> Christoph Hellwig <hch@infradead.org> writes:
> > Btw, it would be nice if all architectures that have more or less
> > a copy of the i386 irq.c could switch to the generic code.
> >
> > That would be: alpha,ia64, m32r, mips, sh, sh64, um, v850
>
> Er, yeah, hold on (speaking for v850, I generally only ever look at real
> releases and try to update for the next one).
It's not urgent anyway - the old code continues to work, it'd just be nicer
if as many as possible architectures used the common code.
prev parent reply other threads:[~2004-10-25 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0410221431180.2101@ppc970.osdl.org>
2004-10-24 15:54 ` generic hardirq code in 2.6.10-rc1 Christoph Hellwig
2004-10-25 6:02 ` Miles Bader
2004-10-25 12:36 ` Christoph Hellwig [this message]
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=20041025123624.GA32463@infradead.org \
--to=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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