From: Pavel Machek <pavel@ucw.cz>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: any interest in unreferenced header files throughout the tree?
Date: Sun, 4 Oct 2009 20:56:55 +0200 [thread overview]
Message-ID: <20091004185655.GB1378@ucw.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.0909291906060.9535@localhost>
On Tue 2009-09-29 19:11:55, Robert P. J. Day wrote:
>
> 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.
Better yet post it to the list.
And if there are headers that are unused now and were unused in
2.6.25... I guess you can just submit patch removing those.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-10-04 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 23:11 Robert P. J. Day
2009-10-04 18:56 ` Pavel Machek [this message]
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=20091004185655.GB1378@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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®