From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Colin Cross <ccross@android.com>
Cc: Len Brown <lenb@kernel.org>, Len Brown <len.brown@intel.com>,
Kevin Hilman <khilman@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuidle: coupled: fix sleeping while atomic in cpu notifier
Date: Wed, 15 Aug 2012 22:16:10 +0200 [thread overview]
Message-ID: <201208152216.10512.rjw@sisk.pl> (raw)
In-Reply-To: <CAMbhsRT5pHkVWPf5u=+hqWhAgAD_kDb+DSSx+PG-nAJ5DHdhng@mail.gmail.com>
On Wednesday, August 08, 2012, Colin Cross wrote:
> On Tue, Aug 7, 2012 at 3:15 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, July 25, 2012, Colin Cross wrote:
> >> The cpu hotplug notifier gets called in both atomic and non-atomic
> >> contexts, it is not always safe to lock a mutex. Filter out all events
> >> except the six necessary ones, which are all sleepable, before taking
> >> the mutex.
> >>
> >> Signed-off-by: Colin Cross <ccross@android.com>
> >
> > Has this been applied already?
>
> It's not in Linus' tree, and I haven't heard anything from Len.
Len appears to be unavailable.
I'll put it into the linux-next branch of the linux-pm.git tree and will
push it to Linus for -rc3 if Len doesn't show up till then.
Thanks,
Rafael
prev parent reply other threads:[~2012-08-15 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 21:20 [PATCH] cpuidle: coupled: fix sleeping while atomic in cpu notifier Colin Cross
2012-07-26 7:25 ` Shilimkar, Santosh
2012-07-26 22:54 ` Shilimkar, Santosh
2012-07-26 19:55 ` Rafael J. Wysocki
2012-07-26 19:51 ` Colin Cross
2012-07-26 20:15 ` Rafael J. Wysocki
2012-07-26 20:16 ` Rafael J. Wysocki
2012-07-31 15:43 ` Srivatsa S. Bhat
2012-07-31 18:27 ` Colin Cross
2012-08-01 5:59 ` Srivatsa S. Bhat
2012-08-07 22:15 ` Rafael J. Wysocki
2012-08-08 0:54 ` Colin Cross
2012-08-15 20:16 ` Rafael J. Wysocki [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=201208152216.10512.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ccross@android.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shilimkar@ti.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.