From: Arnd Bergmann <arnd@arndb.de>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: David Howells <dhowells@redhat.com>,
Josh Triplett <josh@joshtriplett.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] bug: When !CONFIG_BUG, simplify WARN_ON_ONCE and family
Date: Mon, 24 Feb 2014 14:39:46 +0100 [thread overview]
Message-ID: <16994526.0QcMcz0xo0@wuerfel> (raw)
In-Reply-To: <20140224131605.3bd7febc@alan.etchedpixels.co.uk>
On Monday 24 February 2014 13:16:05 One Thousand Gnomes wrote:
>
> While I agree defining it as do {} while(1); would be a lot smarter,
> simply making it required that a platform provides an implementation of
> BUG() would be even better.
But how do we get there? The majority of architectures define BUG()
already, but a lot of them only if CONFIG_BUG is enabled. That is
of course trivial do change, and it is what my older patch does
for ARM and x86.
We also have seven architectures without a BUG() implementation (c6x,
m32r, meta, microblaze, score, sh, unicore32) and six more (arm64,
hexagon openrisc tile um xtensa) that have no bug.h at all.
Arnd
next prev parent reply other threads:[~2014-02-24 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 19:23 [PATCH RESEND] bug: When !CONFIG_BUG, simplify WARN_ON_ONCE and family Josh Triplett
2014-02-22 19:23 ` Josh Triplett
2014-02-22 21:54 ` Randy Dunlap
2014-02-22 22:31 ` Josh Triplett
2014-02-22 22:36 ` Josh Triplett
2014-02-24 8:02 ` Arnd Bergmann
2014-02-24 8:02 ` Arnd Bergmann
2014-02-24 8:44 ` Josh Triplett
2014-02-24 8:44 ` Josh Triplett
2014-02-24 9:35 ` Arnd Bergmann
2014-02-24 12:09 ` David Howells
2014-02-24 12:42 ` Arnd Bergmann
2014-02-24 13:16 ` One Thousand Gnomes
2014-02-24 13:39 ` Arnd Bergmann [this message]
2014-02-24 23:17 ` Andrew Morton
2014-02-24 23:17 ` Andrew Morton
2014-02-25 3:06 ` Josh Triplett
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=16994526.0QcMcz0xo0@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=josh@joshtriplett.org \
--cc=linux-arch@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