From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.41 still not testable by end users
Date: 21 Oct 2002 11:59:15 +0100 [thread overview]
Message-ID: <1035197955.27318.32.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3DAF8198.A66E0C82@digeo.com>
On Fri, 2002-10-18 at 04:35, Andrew Morton wrote:
> But it's a bit academic. ia32's request_irq() calls proc_mkdir() and
> create_proc_entry(). So there's no point in feeding gfp_flags down
> into request_irq or whatever. We need to fix IDE still.
I don't plan to fix the IDE layer, or the sound drivers, or the hundred
odd other drivers where this is close to impossible to fix. What is
broken is how we do IRQ setup still being like 0.12 not split.
next prev parent reply other threads:[~2002-10-21 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 2:35 Steve Parker
2002-10-17 2:55 ` Andrew Morton
2002-10-17 22:23 ` Thomas Molina
2002-10-17 22:39 ` Andrew Morton
2002-10-18 2:48 ` Andi Kleen
2002-10-18 3:35 ` Andrew Morton
2002-10-21 10:59 ` Alan Cox [this message]
2002-10-18 8:43 ` Arjan van de Ven
2002-10-21 10:56 ` Alan Cox
2002-10-17 23:15 ` Steve Parker
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=1035197955.27318.32.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@muc.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®