From: Anton Blanchard <anton@samba.org>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, Andrey Panin <pazke@donpac.ru>
Subject: Re: Moving per-arch IRQ handling code into common directories
Date: Sun, 11 Jul 2004 21:09:20 +1000 [thread overview]
Message-ID: <20040711110919.GI5232@krispykreme> (raw)
In-Reply-To: <16602.9814.700745.300562@wombat.chubb.wattle.id.au>
Hi,
> Inside each arch-specific kernel/irq.c, there's a comment something like,
> /* (mostly architecture independent, will move to kernel/irq.c in 2.5.) */
>
> This obviously hasn't happened, even though there was a patch by
> Andrey Panin floating about around a year ago. Is there some
> fundamental objection to consolidating the IRQ handling as far as
> possible, or was it just that the patch didn't get high enough profile?
I think it died because we were in a freeze at the time. Id like to see
it happen again, perhaps we can get something together to go into -mm.
Anton
next prev parent reply other threads:[~2004-07-11 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 0:54 Moving per-arch IRQ handling code into common directories Peter Chubb
2004-07-11 11:09 ` Anton Blanchard [this message]
2004-07-12 4:59 ` Andrey Panin
2004-08-02 15:54 ` Anton Blanchard
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=20040711110919.GI5232@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@donpac.ru \
--cc=peterc@gelato.unsw.edu.au \
/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