From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: most popular kernel cleanup scripts now posted
Date: Wed, 10 Mar 2010 05:38:32 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003100535120.4271@localhost> (raw)
http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup_scripts
* unused CONFIG variables: variables defined in a Kconfig* file
somewhere that don't appear to be subsequently used/tested
* badref CONFIG variables: variables used/tested in kernel source
that don't appear to be defined in any Kconfig file
* badref CONFIG variables in Makefile: special case of above, for
variables strictly in Makefiles
* badref "select" directives: Kconfig select directives to
non-existent CONFIG variables
* badref linux header files: inclusions of header files of the form
<linux/whatever.h> where said file does not appear to exist.
please don't make fun of my code. it's very sensitive about that.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2010-03-10 10:40 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=alpine.LFD.2.00.1003100535120.4271@localhost \
--to=rpjday@crashcourse.ca \
--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