From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: any interest in unreferenced header files throughout the tree?
Date: Tue, 29 Sep 2009 19:11:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0909291906060.9535@localhost> (raw)
with a minor tweak to one of my scripts, i can now identify all
header files throughout the source tree that no one seems to be using,
and i can generate that output broken down as usual by logical
subdirectories.
as a simple example, under fs/, there appears to be a single unused
header file:
fs/xfs/xfs_refcache.h
if there's interest, i can generate output for the entire tree and
post it at the normal wiki location.
rday
p.s. there's a *lot* of them under arch/.
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-09-29 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 23:11 Robert P. J. Day [this message]
2009-10-04 18:56 ` any interest in unreferenced header files throughout the tree? Pavel Machek
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.0909291906060.9535@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.