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: <201112152334.16527.rjw@sisk.pl>
Date:	Thu, 15 Dec 2011 23:34:16 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	"Greg Kroah-Hartman" <gregkh@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Russell King <linux@....linux.org.uk>,
	Namhyung Kim <namhyung@...il.com>,
	Alan Stern <stern@...land.harvard.edu>
Subject: [Update][PATCH 0/5] PM: Make the PM core execute driver callbacks if subsystem ones are not present

Hi,

I have one more patch for this series and a couple of fixes.

On Saturday, December 10, 2011, Rafael J. Wysocki wrote:
> 
> The following patchset changes the PM core so that driver callbacks
> are executed automatically when subsystem ones are not present and
> uses the new PM core's behavior to simplify the platform and AMBA bus
> types (there probably are many more bus types that may be simplified
> this way, but those two were the easiest targets for me).
> 
> The reasons why to do this are outlined in the changelog of the second patch.

[1/5] - Make pm_op and pm_noirq_op return callbacks
[2/5] - Make PM core call driver callbacks directly if subsystem ones are not present
[3/5] - Remove unnecessary bus type PM callback from platform bus type
[4/5] - Remove unnecessary bus type PM callback from AMBA bus type
[5/5] - Drop generic_subsys_pm_ops

If there are no objections, I'd like to take these patches for 3.3.

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