From: Joe Perches <joe@perches.com>
To: Jian Peng <jipeng@broadcom.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: two false alarms from checkpatch.pl
Date: Mon, 13 Jun 2011 16:36:33 -0700 [thread overview]
Message-ID: <1308008193.26699.60.camel@Joe-Laptop> (raw)
In-Reply-To: <E18F441196CA634DB8E1F1C56A50A874572DE7E973@IRVEXCHCCR01.corp.ad.broadcom.com>
On Mon, 2011-06-13 at 16:28 -0700, Jian Peng wrote:
> On the other hand,
> while (1);
> is a style that was used universally by C programmers. Could you rethink about take this as exception in checkpatch.pl?
For some subset of C programmers... ;)
The kernel generally uses "unreachable()" instead.
prev parent reply other threads:[~2011-06-13 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 23:18 Jian Peng
2011-06-13 23:23 ` Joe Perches
2011-06-13 23:28 ` Jian Peng
2011-06-13 23:36 ` Joe Perches [this message]
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=1308008193.26699.60.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=jipeng@broadcom.com \
--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
all inboxes | Powered by JetHome®