From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jean Delvare <khali@linux-fr.org>
Cc: Greg KH <gregkh@suse.de>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org
Subject: Re: platform_bus: Allow runtime PM by default
Date: Fri, 23 Apr 2010 20:41:41 +0200 [thread overview]
Message-ID: <201004232041.42064.rjw@sisk.pl> (raw)
In-Reply-To: <201004232026.37114.rjw@sisk.pl>
On Friday 23 April 2010, Rafael J. Wysocki wrote:
> On Friday 23 April 2010, Rafael J. Wysocki wrote:
> > On Friday 23 April 2010, Mark Brown wrote:
> > > On Fri, Apr 23, 2010 at 09:11:57AM -0700, Greg KH wrote:
> > > > On Fri, Apr 23, 2010 at 04:57:21PM +0100, Mark Brown wrote:
> > >
> > > > > Turns out it's commit ad53012 "i2c: Fix bus-level power management
> > > > > callbacks" in the PM tree that it depends on. Does it make sense to
> > > > > merge this via there rather than via your tree?
> > >
> > > > Why would an i2c specific patch be needed here? Do you have a pointer
> > > > to that patch?
> > >
> > > Despite the patch title being I2C specific it actually includes exposing
> > > some of the runtime PM implementation to external users - I2C being the
> > > first user of the generic PM runtime callbacks that I'm trying to use in
> > > the platform device implementation.
> > >
> > > http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commitdiff;h=ad530128cd302e5df930b6eb4d4c7e162c40fcb2;hp=b938b00444e900f1c86e754539e3d00f172c184e
> > > http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commitdiff;h=d690b2cd222afc75320b9b8e9da7df02e9e630ca
> > >
> > > > And yes, if it depends on something else in the PM tree, feel free to
> > > > send this patch also through it, I have no objection to that. Rafael,
> > > > care to pick it up? Mark, you might have to resend it to him.
> > >
> > > OK, Raphael please let me know if you need a resend.
> >
> > No, thanks, I have your original post.
>
> Now applied to suspend-2.6/linux-next .
Reverted, sorry.
The i2c patch is not in my tree, it's in the i2c tree.
Perhaps I can handle the both of them.
Jean, the patch we're discussing depends on the
"i2c: Fix bus-level power management callbacks" patch that's in your tree right
now. Would it be possible to move the i2c patch to my tree, or alternatively
would it be acceptable for you to merge a core PM patch through your tree?
Rafael
next prev parent reply other threads:[~2010-04-23 18:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 17:42 [PATCH/RFC] " Mark Brown
2010-03-26 22:35 ` Rafael J. Wysocki
2010-03-27 19:41 ` Mark Brown
2010-03-27 23:32 ` Rafael J. Wysocki
2010-04-22 23:53 ` Greg KH
2010-04-23 10:57 ` Mark Brown
2010-04-23 15:05 ` Greg KH
2010-04-23 15:13 ` Mark Brown
2010-04-23 15:49 ` Greg KH
2010-04-23 15:57 ` Mark Brown
2010-04-23 16:11 ` Greg KH
2010-04-23 16:28 ` Mark Brown
2010-04-23 16:36 ` Greg KH
2010-04-23 16:40 ` Rafael J. Wysocki
2010-04-23 18:26 ` Rafael J. Wysocki
2010-04-23 18:41 ` Rafael J. Wysocki [this message]
2010-05-07 13:27 ` Mark Brown
2010-05-07 14:20 ` Jean Delvare
2010-05-10 21:10 ` Rafael J. Wysocki
2010-05-11 6:19 ` Jean Delvare
2010-05-11 13:00 ` [linux-pm] " 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=201004232041.42064.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--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
all inboxes | Powered by JetHome®