From: Matt Mackall <mpm@selenic.com>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kernel@vger.kernel.org, dirk.brandewie@gmail.com,
linux-arch@vger.kernel.org, linux-kbuild@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Behavior of BUG() [Was: Re: [PATCH 2/5] of/fdt: add kernel command line option for dtb_compat string]
Date: Tue, 16 Nov 2010 22:07:23 -0600 [thread overview]
Message-ID: <1289966843.26343.359.camel@calx> (raw)
In-Reply-To: <AANLkTinop4_JT4JLtdmWkydPgDDU=TyZNbtiBbgeh1dj@mail.gmail.com>
On Tue, 2010-11-16 at 22:45 -0500, Arnaud Lacombe wrote:
> Hi,
>
> [CC: list reduced as starting a new thread, most on the context
> removed as this concern a different issue.]
>
> On Tue, Nov 16, 2010 at 7:16 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On Tue, Nov 16, 2010 at 3:41 PM, <dirk.brandewie@gmail.com> wrote:
> >> From: Dirk Brandewie <dirk.brandewie@gmail.com>
> >> [...]
> > The kernel needs to complain *loudly* if this occurs because it
> > represents a bug. I'm tempted to say use BUG, but that would halt the
> > kernel and prevent any possibility of kernel log output.
> > [...]
> does it ? if CONFIG_BUG is not enabled and the arch has no define for
> it, the default does _nothing_:
That's because CONFIG_BUG=N is intended for machines where logging is
irrelevant/impossible. You are encouraged to ignore all options under
CONFIG_EMBEDDED when trying to have a sensible discussion.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2010-11-17 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 3:45 Behavior of BUG() [Was: Re: [PATCH 2/5] of/fdt: add kernel command line option for dtb_compat string] Arnaud Lacombe
2010-11-17 3:45 ` Arnaud Lacombe
2010-11-17 4:07 ` Matt Mackall [this message]
2010-11-17 4:07 ` Matt Mackall
2010-11-17 4:20 ` Arnaud Lacombe
2010-11-17 4:20 ` Arnaud Lacombe
2010-11-17 4:13 ` Grant Likely
2010-11-17 4:13 ` Grant Likely
2010-11-17 4:29 ` Arnaud Lacombe
2010-11-17 4:29 ` Arnaud Lacombe
2010-11-17 4:44 ` Matt Mackall
2010-11-17 4:44 ` Matt Mackall
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=1289966843.26343.359.camel@calx \
--to=mpm@selenic.com \
--cc=dirk.brandewie@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=lacombar@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox