From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Thomas Molina <tmolina@cox.net>,
Steve Parker <steve.parker@netops.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.41 still not testable by end users
Date: 18 Oct 2002 10:43:45 +0200 [thread overview]
Message-ID: <1034930625.2300.0.camel@localhost.localdomain> (raw)
In-Reply-To: <3DAF3C36.2065CFD1@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
> request_irq() was changed to use GFP_ATOMIC, so it's "fixed".
Are you sure? Afaik request_irq also changes some files in proc.... are
you sure that is all done atomically ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-18 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 2:35 2.5.41 still not testable by end users 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
2002-10-18 8:43 ` Arjan van de Ven [this message]
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=1034930625.2300.0.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steve.parker@netops.co.uk \
--cc=tmolina@cox.net \
/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