summaryrefslogtreecommitdiffstats
path: root/drivers/net/usb
diff options
context:
space:
mode:
authorBjørn Mork <bjorn@mork.no>2013-04-08 08:26:23 +0000
committerDavid S. Miller <davem@davemloft.net>2013-04-08 16:55:28 -0400
commit67a366064a913dfecc02729b3bd3f9ab9e75470c (patch)
tree6e512f6528b116288b1c9ef9d7db6f8462b9c658 /drivers/net/usb
parent077f02f1baee7c1eed800e95c7bb76a6be5226d4 (diff)
downloadtalos-obmc-linux-67a366064a913dfecc02729b3bd3f9ab9e75470c.tar.gz
talos-obmc-linux-67a366064a913dfecc02729b3bd3f9ab9e75470c.zip
net: cdc_ncm: demote "unexpected notification" to debug level
Receiving unhandled notifications is most certainly not an error and should not be logged as one. Knowing that the device sends notifications we don't handle is useful for developers, but there is very little a user can do about this. The message is therefore just annoying noise to most users with devices sending unhandled notifications like e.g. USB_CDC_NOTIFY_RESPONSE_AVAILABLE Cc: Alexey Orishko <alexey.orishko@stericsson.com> Signed-off-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/usb')
-rw-r--r--drivers/net/usb/cdc_ncm.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/net/usb/cdc_ncm.c
index 44a989cd9fb2..67012cbd5582 100644
--- a/drivers/net/usb/cdc_ncm.c
+++ b/drivers/net/usb/cdc_ncm.c
@@ -1124,8 +1124,9 @@ static void cdc_ncm_status(struct usbnet *dev, struct urb *urb)
break;
default:
- dev_err(&dev->udev->dev, "NCM: unexpected "
- "notification 0x%02x!\n", event->bNotificationType);
+ dev_dbg(&dev->udev->dev,
+ "NCM: unexpected notification 0x%02x!\n",
+ event->bNotificationType);
break;
}
}
OpenPOWER on IntegriCloud