linux-kernel - Re: platform_bus: Allow runtime PM by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201004232041.42064.rjw@sisk.pl>
Date:	Fri, 23 Apr 2010 20:41:41 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Jean Delvare <khali@...ux-fr.org>
Cc:	Greg KH <gregkh@...e.de>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org
Subject: Re: platform_bus: Allow runtime PM by default

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/