From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Thomas Gleixner <tglx@linutronix.de>,
Yegor Yefremov <yegorslists@googlemail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: am335x: d_can: rx issue
Date: Tue, 29 Apr 2014 19:10:28 +0200 [thread overview]
Message-ID: <535FDD04.2050804@hartkopp.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404291102240.6261@ionos.tec.linutronix.de>
On 29.04.2014 11:03, Thomas Gleixner wrote:
> On Tue, 29 Apr 2014, Yegor Yefremov wrote:
>>>> TX is working, but rx not. Am I missing any patches, that fix this issue?
>>>
>>> I bet, TX is not working either. You probably fall over the issue with
>>> the startup logic.
>>>
>>> Does the following patch fix your issue?
>>>
>>> http://patchwork.ozlabs.org/patch/342518/
>>
>> Yes, it does.
>>
>> Thanks.
>>
>> Are these patches going to hit 3.15-rc4?
>
> Marc, can you expedite that one for 3.15 please?
>
Hi Thomas,
Marc is out of office until May 5th.
See: http://marc.info/?l=linux-can&m=139855189427393&w=2
But this requested patch has already been pulled into Dave Millers net-tree:
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=bed11db3d4095e5f818f5e8bf7f43ef2beb36d4e
So it will hit mainline with the next pull request from Dave to Linus.
3.15-rc4 looks therefore really feasible :-)
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
Regards,
Oliver
next prev parent reply other threads:[~2014-04-29 17: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 [this message]
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
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=535FDD04.2050804@hartkopp.net \
--to=socketcan@hartkopp.net \
--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 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.