From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Jan Kasprzak <kas@fi.muni.cz>, Paul Mackerras <paulus@samba.org>,
jt@bougret.hpl.hp.com, javier@tudela.mad.ttd.net,
acpi-devel@lists.sourceforge.net,
linux1394-devel@lists.sourceforge.net, roland@topspin.com,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: [ACPI] inappropriate use of in_atomic()
Date: Fri, 11 Mar 2005 23:26:13 +1100 [thread overview]
Message-ID: <1110543974.5809.98.camel@gaston> (raw)
In-Reply-To: <20050311014601.166ae43d.akpm@osdl.org>
On Fri, 2005-03-11 at 01:46 -0800, Andrew Morton wrote:
> Jan Kasprzak <kas@fi.muni.cz> wrote:
> >
> > This may be the cause of
> >
> > http://bugme.osdl.org/show_bug.cgi?id=4150
>
> Looks that way, yes.
Note that it would be interesting to fix that (I mean the reliability of
is_atomic() or an alternative). I agree it's quite bad to rely on that
in practice, but there are a few corner cases where it's useful (like
oops handling in fbdev's etc...)
Ben.
next prev parent reply other threads:[~2005-03-11 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 4:40 inappropriate use of in_atomic() Andrew Morton
2005-03-11 4:53 ` Roland Dreier
2005-03-11 12:38 ` Arjan van de Ven
2005-03-11 6:25 ` Stephen Rothwell
2005-03-11 9:11 ` [ACPI] " Jan Kasprzak
2005-03-11 9:46 ` Andrew Morton
2005-03-11 12:26 ` Benjamin Herrenschmidt [this message]
2005-03-12 0:13 ` [Linux-fbdev-devel] " Andrew Morton
2005-03-12 0:22 ` Benjamin Herrenschmidt
2005-05-31 0:20 ` Adrian Bunk
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=1110543974.5809.98.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=javier@tudela.mad.ttd.net \
--cc=jt@bougret.hpl.hp.com \
--cc=kas@fi.muni.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=paulus@samba.org \
--cc=roland@topspin.com \
/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