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/mesh.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/mesh.c b/drivers/scsi/mesh.c
index 0a9f4e4..67c660a 100644
--- a/drivers/scsi/mesh.c
+++ b/drivers/scsi/mesh.c
@@ -1018,13 +1018,12 @@ static void handle_reset(struct mesh_state *ms)
 
 static irqreturn_t do_mesh_interrupt(int irq, void *dev_id)
 {
-       unsigned long flags;
        struct mesh_state *ms = dev_id;
        struct Scsi_Host *dev = ms->host;
        
-       spin_lock_irqsave(dev->host_lock, flags);
+       spin_lock(dev->host_lock);
        mesh_interrupt(ms);
-       spin_unlock_irqrestore(dev->host_lock, flags);
+       spin_unlock(dev->host_lock);
        return IRQ_HANDLED;
 }
 
-- 
2.8.1

Reply via email to