From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
USB development list <linux-usb@vger.kernel.org>
Subject: Re: [Update][PATCH] USB / PM: Drop CONFIG_PM_RUNTIME from the USB core
Date: Sat, 29 Nov 2014 23:33:07 +0100 [thread overview]
Message-ID: <1620629.NGrQGDcfut@vostro.rjw.lan> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1411291233560.23420-100000@netrider.rowland.org>
On Saturday, November 29, 2014 12:34:36 PM Alan Stern wrote:
> On Sat, 29 Nov 2014, Rafael J. Wysocki wrote:
>
> > > There are also one or two places in Documentation/usb that mention
> > > CONFIG_PM_RUNTIME.
> >
> > I found this in Documentation/usb/power-management.txt:
> >
> > "Note: Dynamic PM support for USB is present only if the kernel was
> > built with CONFIG_USB_SUSPEND enabled (which depends on
> > CONFIG_PM_RUNTIME). System PM support is present only if the kernel
> > was built with CONFIG_SUSPEND or CONFIG_HIBERNATION enabled.
> >
> > (Starting with the 3.10 kernel release, dynamic PM support for USB is
> > present whenever the kernel was built with CONFIG_PM_RUNTIME enabled.
> > The CONFIG_USB_SUSPEND option has been eliminated.)"
> >
> > but I'm quite unsure how to change it. What about:
> >
> > "System PM support is present only if the kernel was built with CONFIG_SUSPEND
> > or CONFIG_HIBERNATION enabled. Dynamic PM support for USB is present whenever
> > the kernel was built with CONFIG_PM enabled.
> >
> > [Historically, dynamic PM support for USB was present only if the kernel
> > had been built with CONFIG_USB_SUSPEND enabled (which depended on
> > CONFIG_PM_RUNTIME). Starting with the 3.10 kernel release, dynamic PM support
> > for USB was present whenever the kernel was built with CONFIG_PM_RUNTIME
> > enabled. The CONFIG_USB_SUSPEND option had been eliminated.]
>
> That sounds fine. Thanks.
OK, thanks.
I'll add that to the patch and resend it, then.
Rafael
next prev parent reply other threads:[~2014-11-29 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 22:45 [PATCH] USB / PM: Drop CONFIG_PM_RUNTIME from the USB core Rafael J. Wysocki
2014-11-27 22:46 ` Rafael J. Wysocki
2014-11-27 23:05 ` [Update][PATCH] " Rafael J. Wysocki
2014-11-28 16:09 ` Alan Stern
2014-11-29 1:17 ` Rafael J. Wysocki
2014-11-29 17:34 ` Alan Stern
2014-11-29 22:33 ` Rafael J. Wysocki [this message]
2014-11-29 22:47 ` [Update 2x][PATCH] " Rafael J. Wysocki
[not found] ` <4725195.YHuDH3PCnx-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2014-11-30 15:45 ` Alan Stern
2014-12-01 1:12 ` Rafael J. Wysocki
2014-12-01 2:53 ` Greg Kroah-Hartman
2014-12-01 22:30 ` 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=1620629.NGrQGDcfut@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).