From: Aaron Lehmann <aaronl@vitelus.com>
To: Paul Gortmaker <p_gortmaker@yahoo.com>
Cc: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Better BUG() macro - take 2
Date: Thu, 22 Feb 2001 14:41:22 -0800 [thread overview]
Message-ID: <20010222144122.A32257@vitelus.com> (raw)
In-Reply-To: <3A924B83.43133ED2@yahoo.com>
In-Reply-To: <3A924B83.43133ED2@yahoo.com>; from p_gortmaker@yahoo.com on Tue, Feb 20, 2001 at 05:48:35AM -0500
On Tue, Feb 20, 2001 at 05:48:35AM -0500, Paul Gortmaker wrote:
> Ok, it appears that some people want the __FILE__, __LINE__ (or equivalent)
> in BUG() and some don't. Fair enough. I used the existing config option
> CONFIG_DEBUG_ERRORS to allow people to choose. There was also interest
> in having BUG() in a more sensible place (e.g. <linux/kernel.h>) and the
> arch specific part separate (I picked <asm-xxx/system.h>).
>
> This only deals with i386 - wanted to put this out for comment before
> editing for the others. Change for other arch is simple though - just
> remove BUG() from asm/page.h and put the *(int *)0=0; type part of what
> was BUG() into asm/system.h as machine_bug(). Oh, and add the config
> option to arch/*/config.in if it isn't already in use.
I noticed the wasteful strings in the kernel image recently and am
excited about this patch.
However, shouldn't this be fixed for all architectures?
Once that happens and the EXPORT_SYMBOL is #ifdef'd, I hope you submit
this to Alan.
prev parent reply other threads:[~2001-02-22 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 10:48 [PATCH] Better BUG() macro - take 2 Paul Gortmaker
2001-02-21 0:50 ` J . A . Magallon
2001-02-22 22:41 ` Aaron Lehmann [this message]
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=20010222144122.A32257@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
/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.