It is redundant to do irqsave and irqrestore in hardIRQ context, where
it has been in a irq-disabled context.

Signed-off-by: Xiaofei Tan <tanxiao...@huawei.com>
---
 drivers/scsi/BusLogic.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/BusLogic.c b/drivers/scsi/BusLogic.c
index ccb061a..005809e 100644
--- a/drivers/scsi/BusLogic.c
+++ b/drivers/scsi/BusLogic.c
@@ -2880,11 +2880,10 @@ static void blogic_process_ccbs(struct blogic_adapter 
*adapter)
 static irqreturn_t blogic_inthandler(int irq_ch, void *devid)
 {
        struct blogic_adapter *adapter = (struct blogic_adapter *) devid;
-       unsigned long processor_flag;
        /*
           Acquire exclusive access to Host Adapter.
         */
-       spin_lock_irqsave(adapter->scsi_host->host_lock, processor_flag);
+       spin_lock(adapter->scsi_host->host_lock);
        /*
           Handle Interrupts appropriately for each Host Adapter type.
         */
@@ -2952,7 +2951,7 @@ static irqreturn_t blogic_inthandler(int irq_ch, void 
*devid)
        /*
           Release exclusive access to Host Adapter.
         */
-       spin_unlock_irqrestore(adapter->scsi_host->host_lock, processor_flag);
+       spin_unlock(adapter->scsi_host->host_lock);
        return IRQ_HANDLED;
 }
 
-- 
2.8.1

Reply via email to