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>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] PM: make runtime_status attribute not debug-only
Date: Sat, 3 Jul 2010 21:29:24 +0200	[thread overview]
Message-ID: <201007032129.24889.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1007021959520.24201-100000@netrider.rowland.org>

On Saturday, July 03, 2010, Alan Stern wrote:
> On Fri, 2 Jul 2010, Rafael J. Wysocki wrote:
> 
> > On Friday, July 02, 2010, Alan Stern wrote:
> > > This patch (as1404) makes the runtime_status sysfs attribute available
> > > even in the absence of CONFIG_PM_ADVANCED_DEBUG, and it changes the
> > > routine to display "unknown" when runtime PM is disabled for a device.
> > > 
> > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > > 
> > > ---
> > > 
> > > Maybe "unsupported" would be a little better than "unknown".  What do 
> > > you think?
> > 
> > I thought about that.  "Unsupported" seems to suggest that the device/driver
> > doesn't support runtime PM, whiile in fact it may be supported, although it's
> > not enabled at the moment.
> 
> Drivers that support runtime PM generally don't leave it disabled for 
> very long.  IMO this wouldn't be terribly misleading.

Well, whatever.  I'm fine with that either way.

Rafael

  reply	other threads:[~2010-07-03 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 16:51 [PATCH] PM: make runtime_status attribute not debug-only Alan Stern
2010-07-02 18:29 ` Dominik Brodowski
2010-07-02 19:14 ` Rafael J. Wysocki
2010-07-03  0:03   ` Alan Stern
2010-07-03 19:29     ` Rafael J. Wysocki [this message]
2010-07-06 13:58   ` [PATCH ver. 2] " Alan Stern
2010-07-07 22:54     ` 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=201007032129.24889.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux@dominikbrodowski.net \
    --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