From: Sam Ravnborg <sam@ravnborg.org>
To: sparse <linux-sparse@vger.kernel.org>
Subject: Detect unused header files?
Date: Tue, 28 Jul 2009 20:18:04 +0200 [thread overview]
Message-ID: <20090728181803.GA20845@merkur.ravnborg.org> (raw)
In the kernel we would like to avoid all
unused include files.
Especially in the headers we export to userspace.
Are there any easy way we can use sparse to detect
that a specific header file is not used?
I know this will depend on the configuration, but
for the use I have in mind this does matter only a little.
The header files I have in mind will be fully self-contained
as they all include the header files they need to be used.
Sample:
cat foo.h:
#include <linux/types.h>
#include <linux/swab.h>
struct foo {
__u32 bar;
__u32 baz;
};
EOF
Here <linux/swab.h> is obviously not used.
And I would like sparse to flag this...
Sam
next reply other threads:[~2009-07-28 18:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 18:18 Sam Ravnborg [this message]
2009-07-28 20:36 ` Detect unused header files? Christopher Li
2009-07-28 20:36 ` Robert P. J. Day
2009-07-28 20:49 ` Christopher Li
2009-07-28 21:04 ` Sam Ravnborg
2009-07-28 21:38 ` Christopher Li
2009-07-30 10:55 ` Christopher Li
2009-07-30 11:12 ` Derek M Jones
2009-07-30 20:36 ` Sam Ravnborg
2009-08-04 21:49 ` Christopher Li
2009-08-05 6:12 ` Sam Ravnborg
2009-08-06 11:14 ` Marko Kreen
2009-08-06 11:17 ` Robert P. J. Day
2009-08-06 12:16 ` Kamil Dudka
2009-08-06 12:15 ` Robert P. J. Day
2009-08-06 13:01 ` Kamil Dudka
2009-08-06 13:26 ` Michael Stefaniuc
2009-08-06 14:09 ` Robert P. J. Day
2009-08-06 17:39 ` Christopher Li
2009-07-28 20:58 ` Sam Ravnborg
2009-07-28 21:21 ` Christopher Li
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=20090728181803.GA20845@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).