diff options
author | Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com> | 2022-11-11 10:44:49 +0900 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2022-11-17 17:42:38 +0000 |
commit | 7d21fcfb409500dc9b114567f0ef8d30b3190dee (patch) | |
tree | d7e68c5146ce3185a55c06e2b24f1be9d22c1098 /drivers/target | |
parent | ecb8c2580d37dbb641451049376d80c8afaa387f (diff) | |
download | linux-7d21fcfb409500dc9b114567f0ef8d30b3190dee.tar.gz linux-7d21fcfb409500dc9b114567f0ef8d30b3190dee.tar.bz2 linux-7d21fcfb409500dc9b114567f0ef8d30b3190dee.zip |
scsi: mpi3mr: Suppress command reply debug prints
After it receives command reply, mpi3mr driver checks command result. If
the result is not zero, it prints out command information. This debug
information is confusing since they are printed even when the non-zero
result is expected. "Power-on or device reset occurred" is printed for Test
Unit Ready command at drive detection. Inquiry failure for unsupported VPD
page header is also printed. They are harmless but look like failures.
To avoid the confusion, print the command reply debug information only when
the module parameter logging_level has value MPI3_DEBUG_SCSI_ERROR= 64, in
same manner as mpt3sas driver.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20221111014449.1649968-1-shinichiro.kawasaki@wdc.com
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/target')
0 files changed, 0 insertions, 0 deletions