summaryrefslogtreecommitdiffstats
path: root/drivers/net/wan
diff options
context:
space:
mode:
authorColin Ian King <colin.king@canonical.com>2018-08-01 19:22:41 +0200
committerDavid S. Miller <davem@davemloft.net>2018-08-02 23:41:43 +0200
commitafb41bb039656f0cecb54eeb8b2e2088201295f5 (patch)
tree3e99f37263bc376049c617fbf1b5531c7a48966d /drivers/net/wan
parentselftest/net: fix protocol family to work for IPv4. (diff)
downloadlinux-afb41bb039656f0cecb54eeb8b2e2088201295f5.tar.xz
linux-afb41bb039656f0cecb54eeb8b2e2088201295f5.zip
drivers: net: lmc: fix case value for target abort error
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>
Diffstat (limited to 'drivers/net/wan')
-rw-r--r--drivers/net/wan/lmc/lmc_main.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/wan/lmc/lmc_main.c b/drivers/net/wan/lmc/lmc_main.c
index 90a4ad9a2d08..b3a1b6f5c406 100644
--- a/drivers/net/wan/lmc/lmc_main.c
+++ b/drivers/net/wan/lmc/lmc_main.c
@@ -1362,7 +1362,7 @@ static irqreturn_t lmc_interrupt (int irq, void *dev_instance) /*fold00*/
case 0x001:
printk(KERN_WARNING "%s: Master Abort (naughty)\n", dev->name);
break;
- case 0x010:
+ case 0x002:
printk(KERN_WARNING "%s: Target Abort (not so naughty)\n", dev->name);
break;
default: