From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Stephane Grosjean <s.grosjean@peak-system.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
tom_usenet@optusnet.com.au,
Manfred Schlaegl <manfred.schlaegl@gmx.at>
Subject: Re: [BULK]Re: [BULK]Re: [PATCH] can: fix loss of frames due to wrong assumption in raw_rcv
Date: Mon, 06 Jul 2015 19:14:20 +0200 [thread overview]
Message-ID: <559AB76C.5020608@hartkopp.net> (raw)
In-Reply-To: <559A3516.7080404@peak-system.com>
On 06.07.2015 09:58, Stephane Grosjean wrote:
> ${CUSTOMER}'s problem was rather a "loss of frame" issue than an
> "out-of-order" issue... In fact, it seems it was a simple "rookie" error of
> non-testing errno == ENOBUF after having written on the CAN socket.
Thanks for the explanation!
No more sleepless nights :-)
Regards,
Oliver
prev parent reply other threads:[~2015-07-06 17:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 17:21 [PATCH] can: fix loss of frames due to wrong assumption in raw_rcv Manfred Schlaegl
2015-06-20 22:42 ` Oliver Hartkopp
2015-06-22 9:48 ` Manfred Schlaegl
2015-06-22 10:24 ` Oliver Hartkopp
[not found] ` <5588E6FB.5040903@optusnet.com.au>
2015-06-23 8:01 ` Oliver Hartkopp
2015-06-24 2:13 ` Tom Evans
2015-06-24 19:56 ` Oliver Hartkopp
2015-06-25 8:32 ` [BULK]Re: " Stephane Grosjean
2015-06-25 9:36 ` Oliver Hartkopp
2015-06-29 16:13 ` Oliver Hartkopp
2015-07-04 16:54 ` Oliver Hartkopp
2015-07-05 1:18 ` Tom Evans
2015-07-05 18:21 ` Oliver Hartkopp
2015-07-06 5:44 ` Oliver Hartkopp
2015-07-06 6:50 ` Tom Evans
2015-07-06 17:09 ` Oliver Hartkopp
2015-07-06 7:58 ` [BULK]Re: " Stephane Grosjean
2015-07-06 17:14 ` Oliver Hartkopp [this message]
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=559AB76C.5020608@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=manfred.schlaegl@gmx.at \
--cc=mkl@pengutronix.de \
--cc=s.grosjean@peak-system.com \
--cc=tom_usenet@optusnet.com.au \
/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).