From: Nick Warne <nick@linicks.net>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Fix crash case
Date: Wed, 16 Aug 2006 20:19:12 +0100 [thread overview]
Message-ID: <200608162019.12678.nick@linicks.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0608161214380.30053@shark.he.net>
On Wednesday 16 August 2006 20:15, Randy.Dunlap wrote:
> > Sorry for being a noob here - I read LKML to try to learn.
> >
> > What is meant by 'If we are going to BUG()... cover the case
> > of the BUG being compiled out'.
> >
> > What would make BUG(); not being compiled?
>
> It's a config option is EMBEDDED=y:
>
Ah! That option. OK, thanks.
Nick
--
Every program has two purposes:
one for which it was written and another for which it wasn't.
next prev parent reply other threads:[~2006-08-16 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 16:35 PATCH: Fix crash case Alan Cox
2006-08-16 17:39 ` Jan Engelhardt
2006-08-16 19:10 ` Nick Warne
2006-08-16 19:15 ` Randy.Dunlap
2006-08-16 19:19 ` Nick Warne [this message]
2006-08-18 9:51 ` Andi Kleen
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=200608162019.12678.nick@linicks.net \
--to=nick@linicks.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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