From: Christoph Hellwig <hch@infradead.org>
To: Eric Valette <eric.valette@free.fr>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.9-rc2 : hardirq.h broken if PREEMPT enabled
Date: Tue, 14 Sep 2004 09:54:14 +0100 [thread overview]
Message-ID: <20040914095414.A5241@infradead.org> (raw)
In-Reply-To: <41460CC3.6000201@free.fr>; from eric.valette@free.fr on Mon, Sep 13, 2004 at 11:10:27PM +0200
On Mon, Sep 13, 2004 at 11:10:27PM +0200, Eric Valette wrote:
> Christoph Hellwig posted this patch but it was unfortunately not
> included in linux-2.6.9-rc2. As I see oops reports with PREEMPT enabled,
> I think people should make sure to apply this patch first.
>
> <http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1227.html>
this can't lead to an oops, the worst thing that could happen would
be acompile failure. But as about half of the old <asm/hardirq.h> instances
didn't have the include either there's no driver I saw that actually
broke.
prev parent reply other threads:[~2004-09-14 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 21:10 linux-2.6.9-rc2 : hardirq.h broken if PREEMPT enabled Eric Valette
2004-09-14 8:54 ` 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=20040914095414.A5241@infradead.org \
--to=hch@infradead.org \
--cc=eric.valette@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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