From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: how to properly post/disseminate kernel cleanup/janitorial possibilities?
Date: Mon, 27 Apr 2009 16:46:46 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904271637470.4906@localhost.localdomain> (raw)
since i, on an occasional basis, run a set of scanning scripts i
wrote and promptly annoy the crap out of everyone with the results,
i'm open to the proper way to do this scanning and get the results out
there to people who might be interested while not bugging those folks
who aren't.
a while back, a few people suggested a wiki page, while others
disagreed, suggesting that no one will follow a link to a wiki page
and will only read what's directly on the list. grapple, grapple.
in the end (as i'm sure you're aware by now), i post the results
here:
http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup
i'm convinced that there's value in the links i've promoted lately --
scanning Kconfig files for unused or "bad" CONFIG variables, not just
to clean historical cruft out of those files but because, on occasion,
the scanning really does track down typoes and errors.
not quite so critical is a "style" script i wrote, which looks for
places to simplify code by using some of the macros/functions defined
in include/linux/kernel.h. i ran that script again earlier today, and
posted only *some* of the results here:
http://www.crashcourse.ca/wiki/index.php/The_style_script
long story short, i have a *pile* of scripts and sub-scripts i'm happy
to run and post the results of since it takes practically zero time on
my part, i'm just open to what folks think is the most productive way
to do that, and also for any other scanning i can add since, by now,
any other patterns to scan for would just represent adding a line or
two to a script.
thoughts?
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
========================================================================
next reply other threads:[~2009-04-27 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 20:46 Robert P. J. Day [this message]
2009-04-27 21:05 ` Bill Gatliff
2009-04-27 22:20 ` Johannes Weiner
2009-04-28 8:25 ` Jiri Kosina
2009-04-28 10:31 ` Robert P. J. Day
2009-04-29 12:01 ` Jiri Kosina
2009-04-29 13:44 ` Robert P. J. Day
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.0904271637470.4906@localhost.localdomain \
--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
all inboxes | Powered by JetHome®