From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Leb Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH v2] ACPI: Fix resource_lock dead lock in acpi_power_on_device
Date: Fri, 14 Sep 2012 09:21:25 +0800 [thread overview]
Message-ID: <50528695.2090602@intel.com> (raw)
In-Reply-To: <50528516.2020002@intel.com>
On 09/14/2012 09:15 AM, Aaron Lu wrote:
>>
>> Good catch, thanks.
>>
>> I hope Len won't mind if I take it for v3.6.
>>
>
> Yes, that would be good.
> And the commit enters v3.4, so a stable tag may need be added.
>
On another thought, it may not be needed for pre v3.6 kernel as the only
code that uses this interface appeared in v3.6-rc1.
Thanks,
Aaron
next prev parent reply other threads:[~2012-09-14 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 9:07 [PATCH v2] ACPI: Fix resource_lock dead lock in acpi_power_on_device Aaron Lu
2012-09-13 22:26 ` Rafael J. Wysocki
2012-09-14 1:15 ` Aaron Lu
2012-09-14 1:21 ` Aaron Lu [this message]
2012-09-14 19:02 ` Rafael J. Wysocki
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=50528695.2090602@intel.com \
--to=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).