public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH ver. 2] PM: describe kernel policy regarding wakeup defaults
Date: Sun, 13 Jun 2010 00:42:07 +0200	[thread overview]
Message-ID: <201006130042.08005.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1006081724060.1387-100000@iolanthe.rowland.org>

On Tuesday, June 08, 2010, Alan Stern wrote:
> On Tue, 8 Jun 2010, Rafael J. Wysocki wrote:
> 
> > On Tuesday 08 June 2010, Alan Stern wrote:
> > > This patch (as1381b) updates a comment describing the kernel's policy
> > > toward enabling wakeup by default.
> > > 
> > > It also makes device_set_wakeup_capable() actually do something when
> > > CONFIG_PM isn't enabled.  It's not clear this is necessary; however if
> > > it isn't then device_init_wakeup() and device_can_wakeup() should also
> > > be do-nothing routines.  Furthermore, I don't expect this change to
> > > have any noticeable effect -- but if it does then clearly the old
> > > behavior was wrong.
> > > 
> > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > > 
> > > ---
> > > 
> > > Rafael, I don't know if you got the earlier version of this patch.  
> > 
> > I did.
> > 
> > > This one applies against 2.6.35-rc1.
> > 
> > I assume I should replace the old patch with this one.
> 
> Yes.  If nothing else, the merge will be simpler.

Applied to suspend-2.6/linux-next.

Rafael

      reply	other threads:[~2010-06-12 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 19:12 [PATCH ver. 2] PM: describe kernel policy regarding wakeup defaults Alan Stern
2010-06-08 20:57 ` Rafael J. Wysocki
2010-06-08 21:24   ` Alan Stern
2010-06-12 22:42     ` 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=201006130042.08005.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.linux-foundation.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