From: Ben Hutchings <bhutchings@solarflare.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH] cputopology: Add default CPU topology information [3rd try]
Date: Wed, 4 Jun 2008 16:07:07 +0100 [thread overview]
Message-ID: <20080604150705.GC11300@solarflare.com> (raw)
In-Reply-To: <20080603130222.694c5675.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 31 May 2008 22:44:30 +0100
> Ben Hutchings <bhutchings@solarflare.com> wrote:
>
> > Define the macros topology_{physical_package,core}_id() and
> > topology_{thread,core}_siblings() in <asm-generic/topology.h> if they are not
> > already defined.
> >
> > Move inclusion of <asm-generic/topology.h> after definitions of these
> > macros in <asm-powerpc/topology.h> and <asm-x86/topology.h>.
> >
> > Change drivers/base/topology.c to use the topology macros unconditionally and
> > to cope with definitions that aren't lvalues.
>
> Can you please redo this against linux-next?
Will do.
> That tree contains a number of directly conflicting changes. In
> particular, linux-next introduces alternate implementations of
> show_##name and show_##name##_list in topology.c and from a quick peek,
> your change could make them go away again.
I don't see what you're referring to. The only things I'm removing are
the attribute list macros, which are unnecessary if the list of attributes
is constant.
> Please also enhance the changelog so we have some idea of why you're
> actually doing all this. What do we gain? Does it fix a bug? If so,
> what? etc.
I'll go back to the explanatory text from my first version.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
prev parent reply other threads:[~2008-06-04 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 21:44 [PATCH] cputopology: Add default CPU topology information [3rd try] Ben Hutchings
2008-05-31 23:11 ` Vegard Nossum
2008-05-31 23:44 ` Ben Hutchings
2008-06-03 20:02 ` Andrew Morton
2008-06-04 15:07 ` Ben Hutchings [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=20080604150705.GC11300@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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