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-next>] [day] [month] [year] [list]
Date:	Tue, 09 Jul 2013 02:01:55 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Yinghai Lu <yinghai@...nel.org>, Jiang Liu <liuj97@...il.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: [RFC][PATCH 0/8] ACPI / hotplug / PCI: Consolidation of handling notifications (in progress)

Hi,

Following is the current set of acpiphp updates targeted at the consolidation
of device notifications handling and removal of suprefluous infrastructure.
Still on top of 3.10 with ACPI+PM 3.11 material merged on top (I'll rebase it
on top of linux-pm.git/bleeding-edge eventually).

[1/8] Make bus registration and unregistration symmetric.  [Resend]
[2/8] Consolidate acpiphp_enumerate_slots().  [Resend]
[3/8] Fix error code path in register_slot().  [Resend]
[4/8] Introduce hotplug context objects for ACPI device objects corresponding
      to PCI hotplug devices.  [Update]
[5/8] Unified notify handler for hotplug events.  [Resend]
[6/8] Drop acpiphp_handle_to_bridge() and use context objects instead of it.
[7/8] Pass entire hotplug context objects (instead of their fields
      individually) to event handling work functions.
[8/8] Merge hotplug event handling functions.

Comments welcome.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

--
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