From: Adrian Bunk <bunk@stusta.de>
To: Dave Jones <davej@redhat.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, mark.langsdorf@amd.com
Subject: Re: [2.6 patch] unexport phys_proc_id and cpu_core_id
Date: Sat, 9 Jul 2005 05:07:25 +0200 [thread overview]
Message-ID: <20050709030725.GB28243@stusta.de> (raw)
In-Reply-To: <20050602211249.GB23826@redhat.com>
On Thu, Jun 02, 2005 at 05:12:50PM -0400, Dave Jones wrote:
> On Thu, Jun 02, 2005 at 10:48:14PM +0200, Adrian Bunk wrote:
> > On Sat, May 07, 2005 at 03:45:07PM +0200, Andi Kleen wrote:
> > > On Fri, May 06, 2005 at 11:19:14PM +0200, Adrian Bunk wrote:
> > > > Back in January, Andi Kleen added EXPORT_SYMBOL(phys_proc_id), stating:
> > > > This is needed for the powernow k8 driver to manage AMD dual core
> > > > systems.
> > > >
> > > > This EXPORT_SYMBOL was never used.
> > > >
> > > > I asked him on 13 Mar 2005 whether it's really required, but he didn't
> > > > answer to my email.
> > >
> > > It is superceeded now with cpu_core_map[]/cpu_core_id[]
> > > >
> > > > 2.6.12-rc3 adds cpu_core_id with a similarly unused
> > > > EXPORT_SYMBOL(cpu_core_id).
> > > >
> > > > It's OK to export symbols when these exports are required, but unless
> > > > someone can explain why they are required now, they should be removed
> > > > before 2.6.12 and then re-added when they are actually used.
> > >
> > > The dual powernowk8 driver really uses them, although the merging
> > > process seems to be a bit slow.
> > >
> > > Andrew, please don't apply the patch.
> >
> > Is there any time when you expect to submit the dual powernowk8 driver
> > you've added the EXPORT_SYMBOL for five months ago?
> >
> > I'd prefer if we'd not add EXPORT_SYMBOL's before the potential users
> > are available...
>
> powernow-k8 dual-core support got merged a few days ago.
My patch to unexport these two variables wouldn't break it today...
> Dave
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
next prev parent reply other threads:[~2005-07-09 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 21:19 [2.6 patch] unexport phys_proc_id and cpu_core_id Adrian Bunk
2005-05-07 13:45 ` Andi Kleen
2005-06-02 20:48 ` Adrian Bunk
2005-06-02 21:12 ` Dave Jones
2005-07-09 3:07 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-30 20:17 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=20050709030725.GB28243@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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