From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
To: Matthias Fuchs <matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
Cc: Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Linux Netdev List
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Subject: Re: can: expected receive behavior broken
Date: Thu, 29 Jul 2010 13:16:46 +0200 [thread overview]
Message-ID: <4C51631E.4000708@hartkopp.net> (raw)
In-Reply-To: <4C514BAE.4070201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
On 29.07.2010 11:36, Oliver Hartkopp wrote:
> Invoking tst-rcv-own-msgs produces this output, which is far away from the
> correct (wanted) output seen in the commit message below.
>
> sockopt default
> s : 0
> t : 0
> timeout
> sockopt - -
> timeout
> sockopt - R
> timeout
> sockopt L -
> s : 3
> t : 3
> timeout
> sockopt L R
> s : 4
> t : 4
> timeout
> done.
>
> I'll check that with the latest linux-2.6 (after rebooting :-)
Grr - it is also broken in 2.6.34-rc7-05126-g278554b ...
I'll go and hunt the bad commit in 2.6.34 and will fix it.
Tnx & regards,
Oliver
> It needs a vcan0 virtual CAN network interface and should produce an output
> like this, when invoked:
>
> sockopt default
> t : 0
> timeout
> sockopt - -
> timeout
> sockopt - R
> timeout
> sockopt L -
> t : 3
> timeout
> sockopt L R
> s : 4
> t : 4
> timeout
> done.
>
prev parent reply other threads:[~2010-07-29 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 7:56 can: expected receive behavior broken Matthias Fuchs
[not found] ` <201007280956.38957.matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
2010-07-28 8:17 ` Wolfgang Grandegger
[not found] ` <4C4FE7AC.4010806-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2010-07-28 8:23 ` Matthias Fuchs
[not found] ` <201007281023.25039.matthias.fuchs-iOnpLzIbIdM@public.gmane.org>
2010-07-29 9:36 ` Oliver Hartkopp
[not found] ` <4C514BAE.4070201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2010-07-29 11:16 ` 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=4C51631E.4000708@hartkopp.net \
--to=socketcan-fj+pqtutwrtk1umjsbkqmq@public.gmane.org \
--cc=Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=matthias.fuchs-iOnpLzIbIdM@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.