From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Olivier Sobrie <olivier@sobrie.be>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: can: kvaser_usb: Add support for Kvaser CAN/USB devices
Date: Sat, 21 Nov 2015 13:40:05 +0100 [thread overview]
Message-ID: <56506625.50003@hartkopp.net> (raw)
In-Reply-To: <20151120081921.GA32659@thinkoso.home>
Hello Olivier,
On 11/20/2015 09:19 AM, Olivier Sobrie wrote:
> No it wasn't intentional. I think that it was inspired from other CAN
> drivers. I see the same in net/can/c_can/c_can.c and
> net/can/m_can/m_can.c. Sorry for the error.
> Btw, which static checker are you using?
>
> As suggested by Oliver, I assume we can transform this in
> cf->data[3] = CAN_ERR_PROT_LOC_CRC_SEQ;
> and fix all the other places where bitwise operations are done
> for errors in data[3].
>
> Should I send a patch to fix this? Or do you or someone else plan
> to send a patch?
I already prepared a patch to fix the data[3] assignment issue.
It's a bunch of drivers that do it wrong:
drivers/net/can/c_can/c_can.c:
drivers/net/can/cc770/cc770.c:
drivers/net/can/flexcan.c:
drivers/net/can/m_can/m_can.c:
drivers/net/can/pch_can.c:
drivers/net/can/rcar_can.c:
drivers/net/can/ti_hecc.c:
drivers/net/can/usb/kvaser_usb.c:
drivers/net/can/usb/usb_8dev.c:
drivers/net/can/xilinx_can.c:
So if it's ok for you I'll post it this weekend :-)
Best regards,
Oliver
next prev parent reply other threads:[~2015-11-21 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 12:42 can: kvaser_usb: Add support for Kvaser CAN/USB devices Dan Carpenter
2015-11-19 13:23 ` Marc Kleine-Budde
2015-11-19 13:46 ` Oliver Hartkopp
2015-11-20 8:19 ` Olivier Sobrie
2015-11-20 11:10 ` Dan Carpenter
2015-11-21 12:40 ` Oliver Hartkopp [this message]
2015-11-21 13:39 ` Olivier Sobrie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56506625.50003@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=dan.carpenter@oracle.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=olivier@sobrie.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).