From: Todd Poynor <toddpoy...@google.com>

Devices not using MSIX don't use the msix_initialized field, so don't
require it to be set in the interrupt system status check. The general
check for interrupts configured that follows can cover both MSIX and
device-managed interrupts.

Signed-off-by: Todd Poynor <toddpoy...@google.com>
---
 drivers/staging/gasket/gasket_interrupt.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/staging/gasket/gasket_interrupt.c 
b/drivers/staging/gasket/gasket_interrupt.c
index 2cd262be65ca0..49d47afad64fa 100644
--- a/drivers/staging/gasket/gasket_interrupt.c
+++ b/drivers/staging/gasket/gasket_interrupt.c
@@ -478,11 +478,6 @@ int gasket_interrupt_system_status(struct gasket_dev 
*gasket_dev)
                return GASKET_STATUS_DEAD;
        }
 
-       if (!gasket_dev->interrupt_data->msix_configured) {
-               dev_dbg(gasket_dev->dev, "Interrupt not initialized\n");
-               return GASKET_STATUS_LAMED;
-       }
-
        if (gasket_dev->interrupt_data->num_configured !=
                gasket_dev->interrupt_data->num_interrupts) {
                dev_dbg(gasket_dev->dev,
-- 
2.19.0.397.gdd90340f6a-goog

Reply via email to