On 09/17/2012 02:02 AM, Yinghai Lu wrote:
> On Sun, Sep 16, 2012 at 9:49 AM, Yinghai Lu wrote:
>> On Sun, Sep 16, 2012 at 7:09 AM, Jiang Liu wrote:
>>> @@ -160,10 +160,13 @@ static int acpi_bind_one(struct device *dev,
>>> acpi_handle handle)
>>> }
>>> dev->archdata.acpi_handle =
On Sun, Sep 16, 2012 at 11:02 AM, Yinghai Lu wrote:
> On Sun, Sep 16, 2012 at 9:49 AM, Yinghai Lu wrote:
>> On Sun, Sep 16, 2012 at 7:09 AM, Jiang Liu wrote:
>>> @@ -160,10 +160,13 @@ static int acpi_bind_one(struct device *dev,
>>> acpi_handle handle)
>>> }
>>> dev->archdata.ac
On Sun, Sep 16, 2012 at 9:49 AM, Yinghai Lu wrote:
> On Sun, Sep 16, 2012 at 7:09 AM, Jiang Liu wrote:
>> @@ -160,10 +160,13 @@ static int acpi_bind_one(struct device *dev,
>> acpi_handle handle)
>> }
>> dev->archdata.acpi_handle = handle;
>>
>> - acpi_pci_bind_notify(dev->
On Sun, Sep 16, 2012 at 7:09 AM, Jiang Liu wrote:
> Now ACPI devices are created before/destroyed after corresponding PCI
> devices, and acpi_platform_notify/acpi_platform_notify_remove will
> update PCI<->ACPI binding relationship when creating/destroying PCI
> devices, there's no need to invoke
Now ACPI devices are created before/destroyed after corresponding PCI
devices, and acpi_platform_notify/acpi_platform_notify_remove will
update PCI<->ACPI binding relationship when creating/destroying PCI
devices, there's no need to invoke bind/unbind callbacks from ACPI
device probe/destroy routin
5 matches
Mail list logo