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: <20100423161157.GA20971@suse.de>
Date:	Fri, 23 Apr 2010 09:11:57 -0700
From:	Greg KH <gregkh@...e.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Greg KH <greg@...ah.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org
Subject: Re: platform_bus: Allow runtime PM by default

On Fri, Apr 23, 2010 at 04:57:21PM +0100, Mark Brown wrote:
> 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:
> 
> > > > Care to fix it up?
> 
> > > 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?
> 
> 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?

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.

thanks,

greg k-h
--
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/