From: Michael Ellerman <michael@ellerman.id.au>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Srinivasa Ds <srinivasa@in.ibm.com>,
Nathan Lynch <ntl@pobox.com>,
paulus@samba.org
Subject: Re: [PATCH]: wrap cpu_die() with CONFIG_HOTPLUG_CPU
Date: Fri, 17 Nov 2006 09:34:57 +1100 [thread overview]
Message-ID: <1163716498.16815.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20061116214114.GE23600@austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On Thu, 2006-11-16 at 15:41 -0600, Linas Vepstas wrote:
> Paul,
>
> Please apply; this is an updated patch per Michael Ellerman,
> below.
>
> --linas
>
> On Thu, Nov 16, 2006 at 10:58:45AM +1100, Michael Ellerman wrote:
> >
> > Thanks for writing it up as a patch. Couple of nit-picky comments below:
>
> Nitpicking's OK.
>
> > +#else
> > #define pSeries_mach_cpu_die NULL
> > > +#endif
> >
> > Not sure if that's a good idea, it would save the #ifdef around the
> > structure assignment below.
>
> Hmm. Personally, I find the #ifdef in the structure to be more
> readable, in the sense that one is less likely to mis-read what
> the code is actually doing, when on is skimming quickly. But,
> not worth arguing over. The patch below incorporates your
> suggestions.
Yeah, it's a trade off, I'm not 100% sure it's a good idea - but we'll
see what others think :)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-11-16 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 18:57 [PATCH]: wrap cpu_die() with CONFIG_HOTPLUG_CPU Linas Vepstas
2006-11-15 23:58 ` Michael Ellerman
2006-11-16 21:41 ` Linas Vepstas
2006-11-16 22:34 ` Michael Ellerman [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=1163716498.16815.3.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.org \
--cc=srinivasa@in.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;
as well as URLs for NNTP newsgroup(s).