From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add BUG_ON to 2.4 #1
Date: Sat, 26 Jan 2002 03:17:33 +0000 [thread overview]
Message-ID: <20020126031732.GA59924@compsoc.man.ac.uk> (raw)
In-Reply-To: <1012000446.3799.77.camel@phantasy>
In-Reply-To: <1012000446.3799.77.camel@phantasy>
On Fri, Jan 25, 2002 at 06:14:05PM -0500, Robert Love wrote:
> The following patch adds the BUG_ON (as seen on TV and 2.5) define to
> the 2.4 kernel. This will help in portability and back-porting from 2.5
> to 2.4, plus BUG_ON is a nice optimization and aids readability.
I mentioned earlier today we need someone to step up and write a kcompat.h
for 2.5 stuff like minor() and the new remap_page_range().
I'll have to do this anyway for the stuff I use (I already have oodles of
2.2 stuff) but it would be nice to be able to use a "standard" header (and .c
if necessary)
regards
john
--
"ALL television is children's television."
- Richard Adler
next prev parent reply other threads:[~2002-01-26 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 23:14 [PATCH] add BUG_ON to 2.4 #1 Robert Love
2002-01-26 3:17 ` John Levon [this message]
2002-01-26 3:22 ` Robert Love
2002-01-26 3:27 ` John Levon
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=20020126031732.GA59924@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.