-20240209 gcc
arc randconfig-001-20240210 gcc
arc randconfig-002-20240209 gcc
arc randconfig-002-20240210 gcc
arcvdk_hs38_smp_defconfig gcc
arm allmodconfig gcc
arm
gcc
arc allnoconfig gcc
arc allyesconfig gcc
arc axs103_smp_defconfig gcc
arc defconfig gcc
arc randconfig-001-20240210 gcc
arc
allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-001-20240210 gcc
arc randconfig-002-20240210 gcc
arcvdk_hs38_smp_defconfig
Do a quick refactor of igb to clean up some unnecessary declarations,
noticed while doing the real work of 2/2.
Follow that with a change of all the Intel drivers to use the current
power management declaration APIs, to avoid complication and maintenance
issues with CONFIG_PM=. This is as per [1]
The igb driver was pre-declaring tons of functions just so that it could
have an early declaration of the pci_driver struct.
Delete a bunch of the declarations and move the struct to the bottom of the
file, after all the functions are declared.
Reviewed-by: Alan Brady
Signed-off-by: Jesse Brande
Switch the Intel networking drivers to use the new power management ops
declaration formats and macros, which allows us to drop __maybe_unused,
as well as a bunch of ifdef checking CONFIG_PM.
This is safe to do because the compiler drops the unused functions,
verified by checking for any of the po
Following the corresponding discussion [1] and [2] refactor the 'igc_open'
method and avoid taking the rtnl_lock() during the 'igc_resume' method.
The rtnl_lock is held by the upper layer and could lead to the deadlock
during resuming from a runtime power management flow. Notify the stack of
the ac
