From: Minchan Kim <minchan.kim@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 1/2] USB / Hub: Do not call device_set_wakeup_capable() under spinlock
Date: Mon, 7 Feb 2011 19:10:18 +0900 [thread overview]
Message-ID: <AANLkTim7Q==ndSRDjAFF+tgRFqFory3Q9nJBPEQKuEEo@mail.gmail.com> (raw)
In-Reply-To: <201102062107.49909.rjw@sisk.pl>
On Mon, Feb 7, 2011 at 5:07 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> A subsequent patch will modify device_set_wakeup_capable() in such
> a way that it will call functions which may sleep and therefore it
> shouldn't be called under spinlocks. In preparation for that, modify
> usb_set_device_state() to avoid calling device_set_wakeup_capable()
> under device_state_lock.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Reported-by: Minchan Kim <minchan.kim@gmail.com>
Tested-by: Minchan Kim <minchan.kim@gmail.com>
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2011-02-07 10:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 14:19 [PATCH] PM: Do not create wakeup sysfs files for devices that cannot wake up (v2) Rafael J. Wysocki
2011-02-06 15:29 ` Alan Stern
2011-02-06 18:53 ` Rafael J. Wysocki
2011-02-06 19:14 ` Greg KH
2011-02-06 20:03 ` Rafael J. Wysocki
2011-02-06 15:50 ` Minchan Kim
2011-02-06 18:54 ` Rafael J. Wysocki
2011-02-06 20:06 ` [PATCH 0/2] PM: Do not create wakeup sysfs files for devices that cannot wake up (v3) Rafael J. Wysocki
2011-02-06 20:07 ` [PATCH 1/2] USB / Hub: Do not call device_set_wakeup_capable() under spinlock Rafael J. Wysocki
2011-02-07 10:10 ` Minchan Kim [this message]
2011-02-06 20:08 ` [PATCH 1/2] PM: Do not create wakeup sysfs files for devices that cannot wake up 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='AANLkTim7Q==ndSRDjAFF+tgRFqFory3Q9nJBPEQKuEEo@mail.gmail.com' \
--to=minchan.kim@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®