From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: first pass of kernel cleanup script for -rc1
Date: Thu, 25 Jun 2009 07:07:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906250704060.12615@localhost> (raw)
now that -rc1 is out, i've started to run my cleanup scripts again.
for now, the only page that's been updated is this one:
http://www.crashcourse.ca/wiki/index.php/Unused_CONFIG_variables
which documents CONFIG variables that are defined in some Kconfig file
but are apparently unused anywhere in the tree. (some false positives
remain, but it's still fairly informative.)
the good news: the output is shrinking from release to release.
the bad news: some of those variables have been there a *long* time.
in any event, enjoy. more cleanup updates will be done today.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-06-25 11:09 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.0906250704060.12615@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