From: Andi Kleen <ak@suse.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk, "Langsdorf,
Mark" <mark.langsdorf@amd.com>,
davej@redhat.com
Subject: Re: [PATCH] [2/2] cpufreq: Fix handling for CPU hotplug
Date: Thu, 2 Mar 2006 02:58:43 +0100 [thread overview]
Message-ID: <200603020258.44224.ak@suse.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB600768EF58@scsmsx403.amr.corp.intel.com>
On Thursday 02 March 2006 02:53, Pallipadi, Venkatesh wrote:
> Thanks for the detailed explanation. I understood most of the code.
> Was only worried whether there is an extra get for CPU 1 in above case,
> just before 0 gets linked to 1. Now, I am convinced that is
> it not the case.
Thanks for the review, Venki. Do you think the patches are suitable
for 2.6.16?
-Andi
next prev parent reply other threads:[~2006-03-02 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 1:53 [PATCH] [2/2] cpufreq: Fix handling for CPU hotplug Pallipadi, Venkatesh
2006-03-02 1:58 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-02 4:39 Pallipadi, Venkatesh
2006-03-01 7:37 shin, jacob
2006-03-01 5:18 Pallipadi, Venkatesh
2006-03-01 3:17 shin, jacob
2006-03-01 1:23 Pallipadi, Venkatesh
2006-02-28 1:54 shin, jacob
2006-02-28 12:17 ` Andi Kleen
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=200603020258.44224.ak@suse.de \
--to=ak@suse.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=mark.langsdorf@amd.com \
--cc=venkatesh.pallipadi@intel.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 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.