From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Yegor Yefremov <yegorslists@googlemail.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: am335x: d_can: rx issue
Date: Wed, 30 Apr 2014 08:08:59 +0200 [thread overview]
Message-ID: <2457559.6qzT8616qY@ws-stein> (raw)
In-Reply-To: <alpine.DEB.2.02.1404291947280.6261@ionos.tec.linutronix.de>
On Tuesday 29 April 2014 19:50:00, Thomas Gleixner wrote:
> On Tue, 29 Apr 2014, Oliver Hartkopp wrote:
> > 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.
>
> It's possible in theory and you can "enforce" it by injecting
> artificial delays, but I doubt it's a real world issue.
>
> Fine with me to remove it along with the accompanying code cruft.
I dont have any objections too removing it.
Regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
prev parent reply other threads:[~2014-04-30 6:10 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
2014-04-29 17:50 ` Thomas Gleixner
2014-04-30 6:08 ` Alexander Stein [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=2457559.6qzT8616qY@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--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 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.