Re: [PATCH] can: dev: increase bus-off message severity

2018-04-25 Thread Marc Kleine-Budde
On 04/18/2018 04:10 PM, Jakob Unterwurzacher wrote: > bus-off is usually caused by hardware malfunction or > configuration error (baud rate mismatch) and causes a > complete loss of communication. > > Increase the "bus-off" message's severity from netdev_dbg > to netdev_info to make it visible to

Re: [PATCH] can: dev: increase bus-off message severity

2018-04-25 Thread Marc Kleine-Budde
On 04/18/2018 04:10 PM, Jakob Unterwurzacher wrote: > bus-off is usually caused by hardware malfunction or > configuration error (baud rate mismatch) and causes a > complete loss of communication. > > Increase the "bus-off" message's severity from netdev_dbg > to netdev_info to make it visible to

[PATCH] can: dev: increase bus-off message severity

2018-04-18 Thread Jakob Unterwurzacher
bus-off is usually caused by hardware malfunction or configuration error (baud rate mismatch) and causes a complete loss of communication. Increase the "bus-off" message's severity from netdev_dbg to netdev_info to make it visible to the user. A can interface going into bus-off is similar in

[PATCH] can: dev: increase bus-off message severity

2018-04-18 Thread Jakob Unterwurzacher
bus-off is usually caused by hardware malfunction or configuration error (baud rate mismatch) and causes a complete loss of communication. Increase the "bus-off" message's severity from netdev_dbg to netdev_info to make it visible to the user. A can interface going into bus-off is similar in