From: Tilman Schmidt <tilman@imap.cc>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, apw@canonical.com
Subject: Re: [PATCH] checkpatch: Add check for too short Kconfig descriptions
Date: Sat, 20 Mar 2010 14:31:30 +0100 [thread overview]
Message-ID: <4BA4CE32.1020207@imap.cc> (raw)
In-Reply-To: <20100320023216.GA917@basil.fritz.box>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 2010-03-20 03:32 schrieb Andi Kleen:
> I've seen various new Kconfigs with rather unhelpful one liner
> descriptions. Add a Kconfig warning for a minimum length of the
> Kconfig help section.
I don't think helpfulness can be enforced via line count.
A one-liner can be quite sufficient (eg. CRYPTO_MD4).
OTOH more lines can still leave important questions unanswered (eg.
CRYPTO_SALSA20_586 whose help text is identical to that of
CRYPTO_SALSA20, leaving you wondering when to choose one over the other).
Jm2c
Tilman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkukzjIACgkQQ3+did9BuFvE1wCff7n2x/bAbiZrJkTnQrEUi7eI
oVsAoJO6l5JMBddFfQOwQDetun1tCtEx
=qkDo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-20 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 2:32 [PATCH] checkpatch: Add check for too short Kconfig descriptions Andi Kleen
2010-03-20 13:31 ` Tilman Schmidt [this message]
2010-03-20 14:07 ` Andi Kleen
2010-03-20 17:24 ` Tilman Schmidt
2010-03-20 18:03 ` Andi Kleen
2010-03-24 12:29 ` Tilman Schmidt
2010-03-24 13:39 ` Andi Kleen
2010-03-24 22:31 ` Tilman Schmidt
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=4BA4CE32.1020207@imap.cc \
--to=tilman@imap.cc \
--cc=andi@firstfloor.org \
--cc=apw@canonical.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