From: Olivier Sobrie <olivier@sobrie.be>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Jonas Peterson <jonas.peterson@gmail.com>, linux-can@vger.kernel.org
Subject: Re: [PATCH v3] can: kvaser_usb: handle rx msg correctly
Date: Wed, 15 May 2013 13:50:25 +0200 [thread overview]
Message-ID: <20130515114907.GA17776@hposo> (raw)
In-Reply-To: <51935DEB.8080805@pengutronix.de>
Hi Marc,
On Wed, May 15, 2013 at 12:05:31PM +0200, Marc Kleine-Budde wrote:
> On 05/07/2013 10:05 PM, Olivier Sobrie wrote:
> > From: Jonas Peterson <jonas.peterson@gmail.com>
> >
> > Unlike Kvaser Leaf light devices, some other Kvaser devices (like USBcan
> > Pro, USBcan R) receive CAN messages in CMD_LOG_MESSAGE frames. This
> > patch adds support for it.
> >
> > Signed-off-by: Jonas Peterson <jonas.peterson@gmail.com>
> > Signed-off-by: Olivier Sobrie <olivier@sobrie.be>
> > ---
> > v3:
> > - add KVASER_EXTENDED_FRAME define
> > - call kvaser_usb_rx_error() in kvaser_usb_rx_can_msg when the frame is
> > a CMD_LOG_MESSAGE and flag MSG_FLAG_ERROR_FRAME is set.
> >
> > By reading the patch again I saw that I mixed up kvaser_usb_rx_can_msg and
> ^^^
>
> Do you want to merge kvaser_usb_rx_can_msg() or kvaser_usb_rx_can_err()?
No, grrr I mixed up kvaser_usb_rx_can_msg and kvaser_usb_rx_can_err in my
comment. I meant kvaser_usb_rx_can_err() and kvaser_usb_rx_error().
>
> > kvaser_usb_rx_error when I cleaned the patch... If fixed that in this
> > version.
> > I should maybe merge these two functions to avoid confusion...
>
> If you want to merge kvaser_usb_rx_can_err() and kvaser_usb_rx_error()
> it would make sense, to have the error handling functionality in one
> function. I haven't looked at the code, though.
Yes that's what I'll maybe do, merging the two error functions in one.
I'll look at this more deeply when I've a more time.
>
> However, this would be a separate patch. I'm applying this patch as it
> is to can/master with linux-stable on Cc.
Ok fine for me.
Thanks,
--
Olivier
next prev parent reply other threads:[~2013-05-15 11:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:50 Patch for kvaser_usb Jonas Peterson
2013-04-26 15:00 ` Marc Kleine-Budde
2013-04-26 16:35 ` Jonas Peterson
2013-04-26 20:51 ` Olivier Sobrie
2013-04-29 7:53 ` Marc Kleine-Budde
2013-04-29 10:40 ` flexcan driver: tx_bytes counter never incremented when CAN_RAW_LOOPBACK removed? Stephane Grosjean
2013-04-29 10:53 ` Marc Kleine-Budde
2013-04-29 12:37 ` Stephane Grosjean
2013-04-29 12:44 ` Marc Kleine-Budde
2013-04-29 12:55 ` Wolfgang Grandegger
2013-04-30 6:47 ` Stephane Grosjean
2013-04-30 10:19 ` Wolfgang Grandegger
2013-04-30 11:37 ` Wolfgang Grandegger
2013-04-29 13:43 ` Kurt Van Dijck
2013-04-29 7:52 ` Patch for kvaser_usb Marc Kleine-Budde
2013-04-29 11:09 ` Jonas Peterson
2013-04-30 21:40 ` [PATCH] can: kvaser_usb: handle rx msg correctly Olivier Sobrie
2013-05-02 10:35 ` Marc Kleine-Budde
2013-05-02 18:06 ` Olivier Sobrie
2013-05-02 18:57 ` [PATCH v2] " Olivier Sobrie
2013-05-03 9:51 ` Marc Kleine-Budde
2013-05-07 20:05 ` [PATCH v3] " Olivier Sobrie
2013-05-15 10:05 ` Marc Kleine-Budde
2013-05-15 11:50 ` Olivier Sobrie [this message]
2013-05-03 9:49 ` [PATCH] " Marc Kleine-Budde
2013-05-06 20:00 ` 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=20130515114907.GA17776@hposo \
--to=olivier@sobrie.be \
--cc=jonas.peterson@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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