From: Johannes Berg <johannes@sipsolutions.net>
To: Andy Whitcroft <apw@shadowen.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: checkpatch suggestion
Date: Mon, 27 Jul 2009 11:50:27 +0200 [thread overview]
Message-ID: <1248688227.19945.49.camel@johannes.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
Occasionally, but far more often than I'd like, we see user-visible
Kconfig symbols enter the tree that have no help text.
I don't know how easy/hard this is, but it'd be nice if checkpatch
caught those. Maybe that would reduce it somewhat.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2009-07-27 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1248688227.19945.49.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=apw@shadowen.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
all inboxes | Powered by JetHome®