From: Ralf Baechle <ralf@uni-koblenz.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: 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 13:41:48 +0100 [thread overview]
Message-ID: <20021104134148.B19377@bacchus.dhis.org> (raw)
In-Reply-To: <20021104022350.DB97A2C0C0@lists.samba.org>; from rusty@rustcorp.com.au on Mon, Nov 04, 2002 at 01:22:45PM +1100
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.
Ralf
next prev parent reply other threads:[~2002-11-04 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 2:22 Rusty Russell
2002-11-04 2:43 ` William Lee Irwin III
2002-11-04 12:41 ` Ralf Baechle [this message]
2002-11-04 12:51 ` Russell King
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=20021104134148.B19377@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®