public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jean Delvare <khali@linux-fr.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	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: Mon, 10 May 2010 23:10:55 +0200	[thread overview]
Message-ID: <201005102310.55838.rjw@sisk.pl> (raw)
In-Reply-To: <20100507162028.022a737c@hyperion.delvare>

On Friday 07 May 2010, Jean Delvare wrote:
> Hi Mark,
> 
> On Fri, 7 May 2010 14:27:46 +0100, Mark Brown wrote:
> > On Fri, Apr 23, 2010 at 08:41:41PM +0200, Rafael J. Wysocki wrote:
> > 
> > > 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?
> > 
> > Jean, any updates on this?
> 
> I'm sorry, I never received Rafael's initial message. I just checked
> through my mailbox and it isn't there.
> 
> The current status is that patch "i2c: Fix bus-level power management
> callbacks" is currently queued in my i2c tree at:
> ftp://ftp.kernel.org/pub/linux/kernel/people/jdelvare/linux-2.6/jdelvare-i2c/i2c-fix-bus-level-power-management-callbacks.patch
> and is scheduled to be merged in 2.6.35-rc1. If this isn't OK, we can
> change the plan.
> 
> Merging a core PM patch through the i2c tree would be quite confusing,
> I think, and might draw even more odd dependencies. So I'd rather have
> the i2c patch moved to the PM staging tree (or whatever tree the
> dependent patch lives in.) Just let me know and I'll drop my copy.

The patch above has been applied to suspend-2.6/linux-next along with the
Mark's $subject patch.

I have converted your sign-off into an ack, hope that's fine.

Thanks,
Rafael

  reply	other threads:[~2010-05-10 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 17:42 [PATCH/RFC] platform_bus: Allow runtime PM by default 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
2010-05-07 13:27                   ` Mark Brown
2010-05-07 14:20                     ` Jean Delvare
2010-05-10 21:10                       ` Rafael J. Wysocki [this message]
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=201005102310.55838.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