From: David Daney <ddaney@caviumnetworks.com>
To: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
David Daney <ddaney@caviumnetworks.com>,
Mike Frysinger <vapier@gentoo.org>,
uclinux-dist-devel@blackfin.uclinux.org
Subject: [PATCH 5/5] blackfin: Convert BUG() to use unreachable()
Date: Thu, 10 Dec 2009 09:28:21 -0800 [thread overview]
Message-ID: <1260466101-17545-5-git-send-email-ddaney@caviumnetworks.com> (raw)
In-Reply-To: <4B212EEC.3060808@caviumnetworks.com>
Use the new unreachable() macro instead of for(;;);
Signed-off-by: David Daney <ddaney@caviumnetworks.com>
CC: Mike Frysinger <vapier@gentoo.org>
CC: uclinux-dist-devel@blackfin.uclinux.org
---
arch/blackfin/include/asm/bug.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/blackfin/include/asm/bug.h b/arch/blackfin/include/asm/bug.h
index 6f4548a..75f6dc3 100644
--- a/arch/blackfin/include/asm/bug.h
+++ b/arch/blackfin/include/asm/bug.h
@@ -47,7 +47,7 @@
#define BUG() \
do { \
_BUG_OR_WARN(0); \
- for (;;); \
+ unreachable(); \
} while (0)
#define WARN_ON(condition) \
--
1.6.2.5
next prev parent reply other threads:[~2009-12-10 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 17:25 [PATCH 0/5] More unreachable() conversions David Daney
2009-12-10 17:28 ` [PATCH 1/5] mn10300: Convert BUG() to use unreachable() David Daney
2009-12-10 17:28 ` [PATCH 2/5] parisc: " David Daney
2009-12-10 21:54 ` Kyle McMartin
2009-12-10 17:28 ` [PATCH 3/5] powerpc: " David Daney
2009-12-10 17:28 ` [PATCH 4/5] alpha: " David Daney
2009-12-11 0:42 ` Matt Turner
2009-12-10 17:28 ` David Daney [this message]
2009-12-10 21:33 ` [Uclinux-dist-devel] [PATCH 5/5] blackfin: " Mike Frysinger
2009-12-10 21:35 ` David Daney
2009-12-10 22:42 ` Mike Frysinger
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=1260466101-17545-5-git-send-email-ddaney@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®