can: fix assignment of error location in CAN error messages
As Dan Carpenter reported in http://marc.info/?l=linux-can&m=144793696016187 the assignment of the error location in CAN error messages had some bit wise overlaps. Indeed the value to be assigned in data[3] is no bitfield but defines a single value which points to a location inside the CAN frame on the wire. This patch fixes the assignments for the error locations in error messages. Reported-by:Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by:
Marc Kleine-Budde <mkl@pengutronix.de>
Showing
- drivers/net/can/c_can/c_can.c 2 additions, 4 deletionsdrivers/net/can/c_can/c_can.c
- drivers/net/can/cc770/cc770.c 1 addition, 1 deletiondrivers/net/can/cc770/cc770.c
- drivers/net/can/flexcan.c 2 additions, 2 deletionsdrivers/net/can/flexcan.c
- drivers/net/can/m_can/m_can.c 2 additions, 4 deletionsdrivers/net/can/m_can/m_can.c
- drivers/net/can/pch_can.c 1 addition, 2 deletionsdrivers/net/can/pch_can.c
- drivers/net/can/rcar_can.c 3 additions, 3 deletionsdrivers/net/can/rcar_can.c
- drivers/net/can/ti_hecc.c 2 additions, 4 deletionsdrivers/net/can/ti_hecc.c
- drivers/net/can/usb/kvaser_usb.c 2 additions, 3 deletionsdrivers/net/can/usb/kvaser_usb.c
- drivers/net/can/usb/usb_8dev.c 1 addition, 2 deletionsdrivers/net/can/usb/usb_8dev.c
- drivers/net/can/xilinx_can.c 2 additions, 3 deletionsdrivers/net/can/xilinx_can.c
Loading
Please register or sign in to comment