From: rpjday@crashcourse.ca (Robert P. J. Day)
To: linux-arm-kernel@lists.infradead.org
Subject: apparently, numerous unused header files under arch/arm
Date: Wed, 30 Sep 2009 04:12:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0909300405080.14643@localhost> (raw)
as part of a new tree scan with one of my scripts, i located what
*appear* to be numerous header files under arch/arm that no one seems
to be including. the first few in that list, accompanied by a full
tree scan of any use of the filename:
===== at91_adc.h =====
./arch/arm/mach-at91/include/mach/at91_adc.h
arch/arm/mach-at91/include/mach/at91_adc.h: * arch/arm/mach-at91/include/mach/at91_adc.h
===== at91_spi.h =====
./arch/arm/mach-at91/include/mach/at91_spi.h
arch/arm/mach-at91/include/mach/at91_spi.h: * arch/arm/mach-at91/include/mach/at91_spi.h
===== at91_ssc.h =====
./arch/arm/mach-at91/include/mach/at91_ssc.h
arch/arm/mach-at91/include/mach/at91_ssc.h: * arch/arm/mach-at91/include/mach/at91_ssc.h
===== aux_reg.h =====
./arch/arm/mach-l7200/include/mach/aux_reg.h
arch/arm/mach-l7200/include/mach/aux_reg.h: * arch/arm/mach-l7200/include/mach/aux_reg.h
===== bast-pmu.h =====
./arch/arm/mach-s3c2410/include/mach/bast-pmu.h
arch/arm/mach-s3c2410/include/mach/bast-pmu.h:/* arch/arm/mach-s3c2410/include/mach/bast-pmu.h
===== board-mx35pdk.h =====
./arch/arm/plat-mxc/include/mach/board-mx35pdk.h
===== board-pcm043.h =====
./arch/arm/plat-mxc/include/mach/board-pcm043.h
===== board-voiceblue.h =====
./arch/arm/plat-omap/include/mach/board-voiceblue.h
... etc etc ...
so, for example, nothing seems to include that last listed
board-voiceblue.h header, not even the source file that's the obvious
candidate: arch/arm/mach-omap1/board-voiceblue.c. and there's lots
more of those. (they're listed in alphabetical order, and i was only
up to the "b"s, but it's almost certain that i'll have some false
positives in there somewhere, perhaps because of Makefile-based
includes.)
is there any interest in my posting that arm-specific list somewhere
and people can peruse it and decide what, if anything, they want to do
with it?
rday
--
========================================================================
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-30 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 8:12 Robert P. J. Day [this message]
2009-09-30 14:46 ` apparently, numerous unused header files under arch/arm David Brown
2009-09-30 18:21 ` Robert P. J. Day
2009-09-30 14:47 ` Bill Gatliff
2009-09-30 15:15 ` 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.0909300405080.14643@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-arm-kernel@lists.infradead.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.