public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport __print_symbol
Date: Tue, 26 Apr 2005 01:02:55 +0200	[thread overview]
Message-ID: <20050425230254.GH4099@stusta.de> (raw)
In-Reply-To: <20050423163518.2dac351c.akpm@osdl.org>

On Sat, Apr 23, 2005 at 04:35:18PM -0700, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> > I didn't find any possible modular usage in the kernel.
> > 
> 
> Making print_symbol() available to modules during their development might
> aid that development.  Presumably, such debug code would not appear in the
> mainline tree.
> 
> IOW: people might want to use print_symbol() during private development, so
> we should continue to export it to modules.

If you need it during private development, you can always re-add it in 
your private tree.

And the possibility of such debug code accidentially getting into 
mainline drops to zero if the EXPORT_SYMBOL isn't there.

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:[~2005-04-25 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 15:10 [2.6 patch] unexport __print_symbol Adrian Bunk
2005-04-23 23:35 ` Andrew Morton
2005-04-25 23:02   ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-04  0:49 Adrian Bunk

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=20050425230254.GH4099@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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