iwlwifi: don't panic in error path on non-msix systems
The driver uses msix causes-register to handle both msix and non msix
interrupts when performing sync nmi. On devices that do not support
msix this register is unmapped and accessing it causes a kernel panic.
Solve this by differentiating the two cases and accessing the proper
causes-register in each case.
Reported-by: Michal Hocko <email@example.com>
Signed-off-by: Shahar S Matityahu <firstname.lastname@example.org>
Signed-off-by: Luca Coelho <email@example.com>
1 file changed