public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: platform_bus: Allow runtime PM by default
Date: Fri, 23 Apr 2010 16:13:27 +0100	[thread overview]
Message-ID: <20100423151327.GA23551@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20100423150528.GB7648@suse.de>

On Fri, Apr 23, 2010 at 08:05:28AM -0700, Greg KH wrote:
> On Fri, Apr 23, 2010 at 11:57:51AM +0100, Mark Brown wrote:

> > This depends on "PM: Provide generic subsystem-level callbacks" which is
> > in Linus' tree - which kernel version are you building against and with
> > what config?  Things work fine for me in -next...

> I was using Linus's latest tree as of yesterday when this failed.  Are
> you relying on something in -next that is not in Linus's tree?

Not intentionally - it's also possible that it's specific to some option
in .config, either an option or something that gets included by default
due to the arch.

  parent reply	other threads:[~2010-04-23 15:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1269625370-17754-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2010-03-26 22:35 ` [PATCH/RFC] platform_bus: Allow runtime PM by default Rafael J. Wysocki
     [not found] ` <201003262335.06941.rjw@sisk.pl>
2010-03-27 19:41   ` Mark Brown
     [not found]   ` <251AAFA3-F44D-40D2-BF99-E82EE58FD52D@opensource.wolfsonmicro.com>
2010-03-27 23:32     ` Rafael J. Wysocki
2010-04-22 23:53 ` Greg KH
2010-04-23 10:57   ` Mark Brown
     [not found]   ` <20100423105750.GA27232@rakim.wolfsonmicro.main>
2010-04-23 15:05     ` Greg KH
     [not found]     ` <20100423150528.GB7648@suse.de>
2010-04-23 15:13       ` Mark Brown [this message]
2010-04-23 15:49         ` Greg KH
2010-04-23 15:57       ` Mark Brown
     [not found]       ` <20100423155721.GG27232@rakim.wolfsonmicro.main>
2010-04-23 16:11         ` Greg KH
     [not found]         ` <20100423161157.GA20971@suse.de>
2010-04-23 16:28           ` Mark Brown
     [not found]           ` <20100423162811.GA31231@rakim.wolfsonmicro.main>
2010-04-23 16:36             ` Greg KH
2010-04-23 16:40             ` Rafael J. Wysocki
     [not found]             ` <201004231840.20041.rjw@sisk.pl>
2010-04-23 18:26               ` Rafael J. Wysocki
     [not found]               ` <201004232026.37114.rjw@sisk.pl>
2010-04-23 18:41                 ` Rafael J. Wysocki
     [not found]                 ` <201004232041.42064.rjw@sisk.pl>
2010-05-07 13:27                   ` Mark Brown
     [not found]                   ` <20100507132746.GA3425@sirena.org.uk>
2010-05-07 14:20                     ` Jean Delvare
     [not found]                     ` <20100507162028.022a737c@hyperion.delvare>
2010-05-10 21:10                       ` Rafael J. Wysocki
     [not found]                       ` <201005102310.55838.rjw@sisk.pl>
2010-05-11  6:19                         ` Jean Delvare
     [not found]                         ` <20100511081900.0e7a1956@hyperion.delvare>
2010-05-11 13:00                           ` Mark Brown

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=20100423151327.GA23551@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    /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