| commit | a6c6516eee1591bc09cf3dd839f71e023dae5ddf | |
| author | Colin Ian King <colin.king@canonical.com> | |
| Wed, 1 Aug 2018 17:22:41 +0000 (1 18:22 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Wed, 5 Sep 2018 07:20:03 +0000 (5 09:20 +0200) | ||
| tree | 701d12b0212afb5daeedccae3823cb2df5c6fa4a | treesnapshot (tar.gz zip) |
| parent | 6b9882c69ee12e1a1437e3ea9fa71edb1d36313f | commitdiff |
drivers: net: lmc: fix case value for target abort error
[ Upstream commit afb41bb039656f0cecb54eeb8b2e2088201295f5 ]
Current value for a target abort error is 0x010, however, this value
should in fact be 0x002. As it stands, the range of error is 0..7 so
it is currently never being detected. This bug has been in the driver
since the early 2.6.12 days (or before).
Detected by CoverityScan, CID#744290 ("Logically dead code")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[ Upstream commit afb41bb039656f0cecb54eeb8b2e2088201295f5 ]
Current value for a target abort error is 0x010, however, this value
should in fact be 0x002. As it stands, the range of error is 0..7 so
it is currently never being detected. This bug has been in the driver
since the early 2.6.12 days (or before).
Detected by CoverityScan, CID#744290 ("Logically dead code")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/net/wan/lmc/lmc_main.c | diffblobblamehistory |