From: Daniel Phillips <phillips@arcor.de>
To: Robert Love <rml@tech9.net>
Cc: Craig Kulesa <ckulesa@as.arizona.edu>,
linux-mm@kvack.org, Andrew Morton <akpm@zip.com.au>,
Ed Tomlinson <tomlins@cam.org>
Subject: Re: slablru for 2.5.32-mm1
Date: Mon, 9 Sep 2002 07:10:22 +0200 [thread overview]
Message-ID: <E17oGoZ-0006mE-00@starship> (raw)
In-Reply-To: <1031546187.15794.19.camel@phantasy>
On Monday 09 September 2002 06:36, Robert Love wrote:
> On Sun, 2002-09-08 at 17:43, Daniel Phillips wrote:
>
> > - if (unlikely((condition)!=0)) BUG(); \
> > + if (unlikely(condition)) BUG(); \
>
> Then send in a patch; the code I pasted was the current 2.5 BUG_ON (and
> 2.4's, since I copied it from 2.5 when I sent the patch). ;-)
Actually, I dimly recall there was a reason for that awkward looking
construct, in which case the bug is a documentation bug. Anybody
remember?
--
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-09 5:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 4:07 Craig Kulesa
2002-09-06 4:24 ` Robert Love
2002-09-08 21:43 ` Daniel Phillips
2002-09-09 4:36 ` Robert Love
2002-09-09 5:10 ` Daniel Phillips [this message]
2002-09-06 4:38 ` Andrew Morton
2002-09-06 11:39 ` Ed Tomlinson
2002-09-06 18:57 ` Craig Kulesa
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 22:11 Ed Tomlinson
2002-08-26 22:09 MM patches against 2.5.31 Ed Tomlinson
2002-08-26 23:58 ` Andrew Morton
2002-08-28 17:06 ` slablru for 2.5.32-mm1 Ed Tomlinson
2002-08-28 21:24 ` Andrew Morton
2002-08-28 22:23 ` Rik van Riel
2002-09-02 5:26 ` Andrew Morton
2002-09-02 15:00 ` Ed Tomlinson
2002-09-02 18:35 ` Andrew Morton
2002-09-02 19:09 ` Ed Tomlinson
2002-09-02 19:51 ` Andrew Morton
2002-09-02 6:50 ` Andrew Morton
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=E17oGoZ-0006mE-00@starship \
--to=phillips@arcor.de \
--cc=akpm@zip.com.au \
--cc=ckulesa@as.arizona.edu \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
--cc=tomlins@cam.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