From: Ram Pai <linuxram@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, arjan@infradead.org, bunk@susta.de,
greg@kroah.com, hch@infradead.org, ilmari@ilmari.org,
mathur@us.ibm.com, sam@ravnborg.org
Subject: Re: [PATCH 1/3] export symbol report: overview
Date: Wed, 26 Apr 2006 12:21:45 -0700 [thread overview]
Message-ID: <1146079305.6430.35.camel@localhost> (raw)
In-Reply-To: <20060422012145.74296470031@localhost>
On Fri, 2006-04-21 at 18:21 -0700, Ram Pai wrote:
> This patch series enables on-demand report generation of export symbol usage by
> inkernel modules.
>
> A report generated by executing
> make allmodconfig
> make exportcheck
> is available at http://www.sudhaa.com/~ram/misc/new_export_report.txt
>
> The same report can also be generated by executing from the top level
> directory:
> perl scripts/export_report.pl
>
> This report lists:
> 1. the usage count of all exported symbols by in-kernel modules.
> 2. For each in-kernel module lists
> a) the in-kernel modules it depend on.
> b) list of exported symbols from that in-kernel modules it depend on.
>
> Highlights:
> On x86 architecture
> (1) 880 exported symbols not used by any in-kernel modules.
> (2) 1792 exported symbols used only once.
>
> Thanks to Adrian Bunk, Arjan, Sam Ravnborg, Dagfinn Ilmari for their
> valuable comments. All comments have been incorporated.
Since I have not heard anything bad about these patches, shall I request
Andrew to apply them to his tree?
RP
next prev parent reply other threads:[~2006-04-26 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 1:21 [PATCH 1/3] export symbol report: overview Ram Pai
2006-04-26 19:21 ` Ram Pai [this message]
2006-04-26 21:29 ` Sam Ravnborg
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=1146079305.6430.35.camel@localhost \
--to=linuxram@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@susta.de \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=ilmari@ilmari.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathur@us.ibm.com \
--cc=sam@ravnborg.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).