[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1289966843.26343.359.camel@calx>
Date: Tue, 16 Nov 2010 22:07:23 -0600
From: Matt Mackall <mpm@...enic.com>
To: Arnaud Lacombe <lacombar@...il.com>
Cc: linux-kernel@...r.kernel.org, dirk.brandewie@...il.com,
linux-arch@...r.kernel.org, linux-kbuild@...r.kernel.org,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: Behavior of BUG() [Was: Re: [PATCH 2/5] of/fdt: add kernel
command line option for dtb_compat string]
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@...retlab.ca> wrote:
> > On Tue, Nov 16, 2010 at 3:41 PM, <dirk.brandewie@...il.com> wrote:
> >> From: Dirk Brandewie <dirk.brandewie@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists