On Tue, 2013-03-26 at 14:11 +0100, Rafael J. Wysocki wrote:
> On Monday, March 04, 2013 02:30:40 PM Toshi Kani wrote:
> > When installing/removing a notify handler to/from an ACPI device
> > object, ACPI core tries to match its associated scan handler to
> > see if it supports hotplug. However,
On Monday, March 04, 2013 02:30:40 PM Toshi Kani wrote:
> When installing/removing a notify handler to/from an ACPI device
> object, ACPI core tries to match its associated scan handler to
> see if it supports hotplug. However, the matching logic of the
> notify handler is different from the
On Monday, March 04, 2013 02:30:40 PM Toshi Kani wrote:
When installing/removing a notify handler to/from an ACPI device
object, ACPI core tries to match its associated scan handler to
see if it supports hotplug. However, the matching logic of the
notify handler is different from the matching
On Tue, 2013-03-26 at 14:11 +0100, Rafael J. Wysocki wrote:
On Monday, March 04, 2013 02:30:40 PM Toshi Kani wrote:
When installing/removing a notify handler to/from an ACPI device
object, ACPI core tries to match its associated scan handler to
see if it supports hotplug. However, the
When installing/removing a notify handler to/from an ACPI device
object, ACPI core tries to match its associated scan handler to
see if it supports hotplug. However, the matching logic of the
notify handler is different from the matching logic of attaching
a scan handler to an ACPI device object.
When installing/removing a notify handler to/from an ACPI device
object, ACPI core tries to match its associated scan handler to
see if it supports hotplug. However, the matching logic of the
notify handler is different from the matching logic of attaching
a scan handler to an ACPI device object.
6 matches
Mail list logo