On Mon, Mar 22, 2021 at 3:32 PM Rafael J. Wysocki wrote:
>
> On Tue, Mar 16, 2021 at 4:52 PM Rafael J. Wysocki wrote:
> >
> > From: Rafael J. Wysocki
> >
> > It should not be necessary to update the current_state field of
> > struct pci_dev in pci_enable_device_flags() before calling
> > do_pci_
On Tue, Mar 16, 2021 at 4:52 PM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> It should not be necessary to update the current_state field of
> struct pci_dev in pci_enable_device_flags() before calling
> do_pci_enable_device() for the device, because none of the
> code between that po
On Tue, Mar 16, 2021 at 04:51:40PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> It should not be necessary to update the current_state field of
> struct pci_dev in pci_enable_device_flags() before calling
> do_pci_enable_device() for the device, because none of the
> code between
On 3/16/21 4:51 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
It should not be necessary to update the current_state field of
struct pci_dev in pci_enable_device_flags() before calling
do_pci_enable_device() for the device, because none of the
code between that point and the pci_set_p
From: Rafael J. Wysocki
It should not be necessary to update the current_state field of
struct pci_dev in pci_enable_device_flags() before calling
do_pci_enable_device() for the device, because none of the
code between that point and the pci_set_power_state() call in
do_pci_enable_device() invoke
5 matches
Mail list logo
