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: <200908132314.47180.rjw@sisk.pl>
Date:	Thu, 13 Aug 2009 23:14:47 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Magnus Damm <magnus.damm@...il.com>, Greg KH <gregkh@...e.de>,
	Pavel Machek <pavel@....cz>, Len Brown <lenb@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>
Subject: Re: [PATCH update 2x] PM: Introduce core framework for run-time PM of I/O devices (rev. 16)

On Thursday 13 August 2009, Paul Mundt wrote:
> On Thu, Aug 13, 2009 at 10:56:42PM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@...k.pl>
> > Subject: PM: Introduce core framework for run-time PM of I/O devices (rev. 16)
> > 
> > Introduce a core framework for run-time power management of I/O
> > devices.  Add device run-time PM fields to 'struct dev_pm_info'
> > and device run-time PM callbacks to 'struct dev_pm_ops'.  Introduce
> > a run-time PM workqueue and define some device run-time PM helper
> > functions at the core level.  Document all these things.
> > 
> > Special thanks to Alan Stern for his help with the design and
> > multiple detailed reviews of the pereceding versions of this patch
> > and to Magnus Damm for testing feedback.
> > 
> > Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
> 
> If there are no more outstanding issues with this, any chance of having
> this rolled in to a topic branch along with Magnus's platform bus
> support? It would be nice if these could spend some time in -next,
> especially as it seems there are no longer any glaring issues with the
> patch series.

I completely agree and I hope there are no major issues with this patch any
more.

If there are no objections, I'm going to put the patch into my linux-next
branch shortly, from where it will go to the for-linus branch.  I'm going to do
that with the Magnus' patch too.

Thanks,
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ