[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210306221232.3382941-2-grundler@chromium.org>
Date: Sat, 6 Mar 2021 14:12:32 -0800
From: Grant Grundler <grundler@...omium.org>
To: Oliver Neukum <oneukum@...e.com>, Jakub Kicinski <kuba@...nel.org>
Cc: Roland Dreier <roland@...nel.org>, nic_swsd <nic_swsd@...ltek.com>,
netdev <netdev@...r.kernel.org>,
"David S . Miller" <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Lunn <andrew@...n.ch>,
Grant Grundler <grundler@...omium.org>
Subject: [PATCH net-next] net: usb: log errors to dmesg/syslog
Errors in protocol should be logged when the driver aborts operations.
If the driver can carry on and "humor" the device, then emitting
the message as debug output level is fine.
Signed-off-by: Grant Grundler <grundler@...omium.org>
---
drivers/net/usb/usbnet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reposting to net-next per instructions in https://www.spinics.net/lists/netdev/msg715496.html
I've applied this patch to most chromeos kernels:
https://chromium-review.googlesource.com/q/hashtag:usbnet-rtl8156-support
diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
index 1447da1d5729..bc7b93399bd5 100644
--- a/drivers/net/usb/usbnet.c
+++ b/drivers/net/usb/usbnet.c
@@ -887,7 +887,7 @@ int usbnet_open (struct net_device *net)
// insist peer be connected
if (info->check_connect && (retval = info->check_connect (dev)) < 0) {
- netif_dbg(dev, ifup, dev->net, "can't open; %d\n", retval);
+ netif_err(dev, ifup, dev->net, "can't open; %d\n", retval);
goto done;
}
--
2.29.2
Powered by blists - more mailing lists