summaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-10-26 15:45:22 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-10-26 15:45:22 -0700
commit4525c8781ec0701ce824e8bd379ae1b129e26568 (patch)
tree9d79fe81bdd401cd890a01e98368bd2dca2689a3 /mm
parentbf9a76a470d83355200adaa5d5b55d118f229ecb (diff)
downloadlinux-4525c8781ec0701ce824e8bd379ae1b129e26568.tar.gz
linux-4525c8781ec0701ce824e8bd379ae1b129e26568.tar.bz2
linux-4525c8781ec0701ce824e8bd379ae1b129e26568.zip
scsi: qla2xxx: remove incorrect sparse #ifdef
The code to try to shut up sparse warnings about questionable locking didn't shut up sparse: it made the result not parse as valid C at all, since the end result now has a label with no statement. The proper fix is to just always lock the hardware, the same way Bart did in commit 8ae178760b23 ("scsi: qla2xxx: Simplify the functions for dumping firmware"). That avoids the whole problem with having locking that is not statically obvious. But in the meantime, just remove the incorrect attempt at trying to avoid a sparse warning that just made things worse. This was exposed by commit 3e6efab865ac ("scsi: qla2xxx: Fix reset of MPI firmware"), very similarly to how commit cbb01c2f2f63 ("scsi: qla2xxx: Fix MPI failure AEN (8200) handling") exposed the same problem in another place, and caused that commit 8ae178760b23. Please don't add code to just shut up sparse without actually fixing what sparse complains about. Reported-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com> Cc: Bart Van Assche <bvanassche@acm.org> Cc: Arun Easi <aeasi@marvell.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions