From: Len Brown <lenb@kernel.org>
To: Toshi Kani <toshi.kani@hp.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Boris Ostrovsky <boris.ostrovsky@amd.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
amit.kucheria@linaro.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpuidle: Fix panic in CPU off-lining with no idle driver
Date: Fri, 06 Apr 2012 14:58:25 -0400 [thread overview]
Message-ID: <4F7F3CD1.9020800@kernel.org> (raw)
In-Reply-To: <4F7B2102.3080006@hp.com>
applied.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2012-04-06 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 3:37 [PATCH] cpuidle: Fix panic in CPU off-lining with no idle driver Toshi Kani
2012-04-03 14:08 ` Srivatsa S. Bhat
2012-04-03 16:10 ` Toshi Kani
2012-04-06 18:58 ` Len Brown [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=4F7F3CD1.9020800@kernel.org \
--to=lenb@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=boris.ostrovsky@amd.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=toshi.kani@hp.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).