From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: am335x: d_can: rx issue
Date: Tue, 29 Apr 2014 19:22:06 +0200 [thread overview]
Message-ID: <535FDFBE.1080007@hartkopp.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404291911470.6261@ionos.tec.linutronix.de>
On 29.04.2014 19:13, Thomas Gleixner wrote:
> On Tue, 29 Apr 2014, Oliver Hartkopp wrote:
>> Btw. I'm currently running Daves net-tree here and was forced to define
>> CONFIG_CAN_C_CAN_STRICT_FRAME_ORDERING during 'make oldconfig' ...
>>
>> Can this Kconfig option probably be removed in the 3.15-rc phase when
>> it's not really needed anymore?
>>
>> See: http://marc.info/?l=linux-can&m=139746476821294&w=2
>
> If it's not necessary for any of the C/DCAN incarnations we can
> probably drop it and rip the code out.
Hm. I don't know. AFAIK only Alexander and you detected and discussed the
frame re-ordering issue of the C_CAN in length.
I put Alexander in CC. When you both don't have any objections it's up to your
opinion to remove this (hopefully) obsolete option.
Best regards,
Oliver
next prev parent reply other threads:[~2014-04-29 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 12:19 am335x: d_can: rx issue Yegor Yefremov
2014-04-28 14:37 ` Thomas Gleixner
2014-04-29 7:30 ` Yegor Yefremov
2014-04-29 9:03 ` Thomas Gleixner
2014-04-29 17:10 ` Oliver Hartkopp
2014-04-29 17:13 ` Thomas Gleixner
2014-04-29 17:22 ` Oliver Hartkopp [this message]
2014-04-29 17:50 ` Thomas Gleixner
2014-04-30 6:08 ` Alexander Stein
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=535FDFBE.1080007@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=tglx@linutronix.de \
--cc=yegorslists@googlemail.com \
/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