public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, arjan@infradead.org,
	greg@kroah.com, hch@infradead.org
Subject: Re: [RFC PATCH 1/2] Makefile: export-symbol usage report generator.
Date: Thu, 20 Apr 2006 03:06:24 +0200	[thread overview]
Message-ID: <20060420010624.GJ25047@stusta.de> (raw)
In-Reply-To: <1145494414.7323.178.camel@localhost>

On Wed, Apr 19, 2006 at 05:53:34PM -0700, Ram Pai wrote:
> On Thu, 2006-04-20 at 01:41 +0200, Adrian Bunk wrote:
> > 
> > - it's a tool for kernel hackers who know what they are doing
> > - it's a tool to help you finding unused exports, but each one still
> >   requires manual verification
> 
> I am not sure I understand you.  Are you saying:
> 
>         A) the tool should report the export symbol usage with whatever
> 		set of modules the user has configured in his .config ?
> 		
> 		or
> 
>         B) the tool should report the export symbol usage for all the
> 	    modules irrespective of what has been configured in the
> 	    users .config ?

A)

> RP

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2006-04-20  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 12:38 [RFC PATCH 1/2] Makefile: export-symbol usage report generator Ram Pai
2006-04-18 14:09 ` Adrian Bunk
2006-04-19 23:25   ` Ram Pai
2006-04-19 23:41     ` Adrian Bunk
2006-04-20  0:53       ` Ram Pai
2006-04-20  1:06         ` Adrian Bunk [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=20060420010624.GJ25047@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    /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