From: Mike Fedyk <mfedyk@matchmail.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@zip.com.au>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: aa-160-lru_release_check
Date: Wed, 20 Mar 2002 11:16:44 -0800 [thread overview]
Message-ID: <20020320191644.GA29857@matchmail.com> (raw)
In-Reply-To: <3C980990.1C6B232A@zip.com.au> <Pine.NEB.4.44.0203201703450.3932-100000@mimas.fachschaften.tu-muenchen.de>
On Wed, Mar 20, 2002 at 05:09:32PM +0100, Adrian Bunk wrote:
> On Tue, 19 Mar 2002, Andrew Morton wrote:
>
> >...
> > + if (unlikely(in_interrupt()))
> > + BUG();
> >...
>
> Is there a reason against intruducing BUG_ON in 2.4? It makes such things
> more readable.
>
I think there are plans to do so...
... But not in this patch.
next prev parent reply other threads:[~2002-03-20 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 4:01 aa-160-lru_release_check Andrew Morton
2002-03-20 16:09 ` aa-160-lru_release_check Adrian Bunk
2002-03-20 19:16 ` Mike Fedyk [this message]
2002-03-20 19:28 ` aa-160-lru_release_check Andrew Morton
2002-03-20 19:38 ` aa-160-lru_release_check Jeff Garzik
2002-03-20 20:02 ` aa-160-lru_release_check Dave Jones
2002-03-20 20:42 ` aa-160-lru_release_check Robert Love
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=20020320191644.GA29857@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@zip.com.au \
--cc=bunk@fs.tum.de \
--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