All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivasa Ds <srinivasa@in.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: ego@in.ibm.com, linuxppc-dev@ozlabs.org,
	Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>,
	ntl@pobox.com, linas@boardhead.austin.ibm.com
Subject: Re: [PATCH] Reorganise and then fixup the pseries cpu hotplug code
Date: Fri, 24 Nov 2006 16:33:14 +0530	[thread overview]
Message-ID: <4566D172.1040505@in.ibm.com> (raw)
In-Reply-To: <20061123021132.B03F767C18@ozlabs.org>

Michael Ellerman wrote:
>
> Updated to printk if we can't find the RTAS tokens, and to remove the
> comment about drslot_chrp_cpu etc.
>
> Linas, Srinivasa, can you test that this addresses the problems you
> were seeing. It should, but it'd be good if you could test it.
>   
 As I was busy this week, I didn't  test your patch. I will do that on 
monday.

Thanks
 Srinivasa DS

  reply	other threads:[~2006-11-24  9:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  2:11 [PATCH] Reorganise and then fixup the pseries cpu hotplug code Michael Ellerman
2006-11-24 11:03 ` Srinivasa Ds [this message]
2006-11-27  8:13 ` Srinivasa Ds
2006-11-27 21:10 ` Linas Vepstas
  -- strict thread matches above, loose matches on Subject: below --
2006-11-16 15:40 [RFC] [PATCH] cpu hotplug on power based systems Nathan Lynch
2006-11-17  3:36 ` [PATCH] Reorganise and then fixup the pseries cpu hotplug code Michael Ellerman
2006-11-17  3:59   ` Michael Ellerman
2006-11-17  4:31   ` Stephen Rothwell
2006-11-17  4:44     ` Michael Ellerman
2006-11-17  5:02       ` Stephen Rothwell
2006-11-17 18:11       ` Linas Vepstas
2006-11-20  0:44         ` Michael Ellerman
2006-11-17 18:04   ` Linas Vepstas
2006-11-20  1:08     ` Michael Ellerman
2006-11-20  4:22       ` jschopp
2006-11-20  5:59         ` Michael Ellerman
2006-11-21 16:43           ` Nathan Lynch

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=4566D172.1040505@in.ibm.com \
    --to=srinivasa@in.ibm.com \
    --cc=anton@samba.org \
    --cc=ego@in.ibm.com \
    --cc=linas@boardhead.austin.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=ntl@pobox.com \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.