diff options
| author | David S. Miller <davem@davemloft.net> | 2019-06-22 04:05:42 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-06-22 04:05:42 +0200 |
| commit | e0effb5fbd56a8b2b8917611cbf4fcd9aba92b8f (patch) | |
| tree | 5db41c7be5d6888479c5d853171951418c3e7e57 /arch/arm/boot/dts/exynos4210.dtsi | |
| parent | Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next (diff) | |
| parent | r8169: don't activate ASPM in chip if OS can't control ASPM (diff) | |
| download | linux-e0effb5fbd56a8b2b8917611cbf4fcd9aba92b8f.tar.xz linux-e0effb5fbd56a8b2b8917611cbf4fcd9aba92b8f.zip | |
Merge branch 'PCI-let-pci_disable_link_state-propagate-errors'
Heiner Kallweit says:
====================
PCI: let pci_disable_link_state propagate errors
Drivers like r8169 rely on pci_disable_link_state() having disabled
certain ASPM link states. If OS can't control ASPM then
pci_disable_link_state() turns into a no-op w/o informing the caller.
The driver therefore may falsely assume the respective ASPM link
states are disabled. Let pci_disable_link_state() propagate errors
to the caller, enabling the caller to react accordingly.
I'd propose to let this series go through the netdev tree if the PCI
core extension is acked by the PCI people.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/arm/boot/dts/exynos4210.dtsi')
0 files changed, 0 insertions, 0 deletions