diff options
| author | Ahmed S. Darwish <a.darwish@linutronix.de> | 2020-11-26 16:29:49 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2020-12-01 08:03:53 +0300 |
| commit | ca6853693cbdcc3f9a38f4544bd3d7b149509784 (patch) | |
| tree | 47c98769165efea7ff3ad7d5ae61e5b601b73e9a /scripts | |
| parent | 3bc08b9545dab900bb5902459877bf6a0fb4ec8b (diff) | |
| download | linux-ca6853693cbdcc3f9a38f4544bd3d7b149509784.tar.xz | |
scsi: myrs: Remove WARN_ON(in_interrupt())
The in_interrupt() macro is ill-defined and does not provide what the name
suggests. The usage especially in driver code is deprecated and a tree-wide
effort to clean up and consolidate the (ab)usage of in_interrupt() and
related checks is happening.
In this case the check covers only parts of the contexts in which these
functions cannot be called. It fails to detect preemption or interrupt
disabled invocations.
As wait_for_completion() already contains a broad variety of checks (always
enabled or debug option dependent) which cover all invalid conditions
already, there is no point in having extra inconsistent warnings in
drivers.
Just remove it.
Link: https://lore.kernel.org/r/20201126132952.2287996-12-bigeasy@linutronix.de
Cc: Hannes Reinecke <hare@kernel.org>
Reviewed-by: Daniel Wagner <dwagner@suse.de>
Signed-off-by: Ahmed S. Darwish <a.darwish@linutronix.de>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions