From: Russell King <rmk@arm.linux.org.uk>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
torvalds@transmeta.com, trivial@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: linux/bug.h and asm/bug.h
Date: Mon, 4 Nov 2002 12:51:15 +0000 [thread overview]
Message-ID: <20021104125115.A15953@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021104134148.B19377@bacchus.dhis.org>; from ralf@uni-koblenz.de on Mon, Nov 04, 2002 at 01:41:48PM +0100
On Mon, Nov 04, 2002 at 01:41:48PM +0100, Ralf Baechle wrote:
> On Mon, Nov 04, 2002 at 01:22:45PM +1100, Rusty Russell wrote:
> > As the number of bug-related macros grows, this makes sense.
> >
> > 1) Introduce linux/bug.h and #include it from linux/kernel.h so noone
> > breaks.
> > 2) Move BUG() macro from asm*/page.h to asm*/bug.h, and #include it.
>
> Great, people were talking about the mess caused by this just last night.
> Just one request, move the BUG_ON definition into <asm/bug.h> also. This
> permits the use of conditional trap instructions for those architecture
> that have them.
I'm a little peeved since everyone's likes this from Rusty, but ignored
exactly the same thing from me. Sigh, life is cruel some times.
Message-Id: E18289f-0007tm-00@flint.arm.linux.org.uk
Subject: [PATCH] 2.5.43-bug
Date: Thu, 17 Oct 2002 11:45:27 +0100
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-11-04 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 2:22 linux/bug.h and asm/bug.h Rusty Russell
2002-11-04 2:43 ` William Lee Irwin III
2002-11-04 12:41 ` Ralf Baechle
2002-11-04 12:51 ` Russell King [this message]
2002-11-04 13:39 ` William Lee Irwin III
2002-11-05 7:49 ` Rusty Russell
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=20021104125115.A15953@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@uni-koblenz.de \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/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.