From: Michael Walle <michael@walle.cc>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Joakim Zhang <qiangqing.zhang@nxp.com>,
linux-can@vger.kernel.org, dl-linux-imx <linux-imx@nxp.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH linux-can-next/flexcan] can: flexcan: fix TDC feature
Date: Mon, 14 Sep 2020 17:16:35 +0200 [thread overview]
Message-ID: <64ec076a31c12218542cfa4fb081e3a7@walle.cc> (raw)
In-Reply-To: <332a98a376e4becf9b10910138034be4@walle.cc>
Hi Marc,
Am 2020-07-23 23:09, schrieb Michael Walle:
> Am 2020-06-25 14:56, schrieb Marc Kleine-Budde:
>> On 6/25/20 2:37 PM, Michael Walle wrote:
>>> Am 2020-06-02 12:15, schrieb Michael Walle:
>>>> Hi Marc,
>>>>
>>>> Am 2020-04-16 11:41, schrieb Joakim Zhang:
>>>>> Hi Marc,
>>>>>
>>>>> How about FlexCAN FD patch set, it is pending for a long time. Many
>>>>> work would base on it, we are happy to see it in upstream mainline
>>>>> ASAP.
>>>>>
>>>>> Michael Walle also gives out the test-by tag:
>>>>> Tested-by: Michael Walle <michael@walle.cc>
>>>>
>>>> There seems to be no activity for months here. Any reason for that?
>>>> Is
>>>> there anything we can do to speed things up?
>>>
>>> ping.. There are no replies or anything. Sorry but this is really
>>> annoying and frustrating.
>>>
>>> Marc, is there anything wrong with the flexcan patches?
>>
>> I've cleaned up the patches a bit, can you test this branch:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=flexcan
>
> Ping. Could we please try to get this into next soon?
>
> See also
> https://lore.kernel.org/netdev/20200629181809.25338-1-michael@walle.cc/
Ping, another 2.5 months without any activity on this :(
-michael
prev parent reply other threads:[~2020-09-14 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 9:31 [PATCH Resend linux-can-next/testing] can: flexcan: add correctable errors correction when HW supports ECC Joakim Zhang
2020-04-16 9:31 ` [PATCH linux-can-next/flexcan] can: flexcan: fix TDC feature Joakim Zhang
2020-04-16 9:41 ` Joakim Zhang
2020-06-02 10:15 ` Michael Walle
2020-06-25 12:37 ` Michael Walle
2020-06-25 12:56 ` Marc Kleine-Budde
2020-06-29 5:37 ` Joakim Zhang
2020-06-29 16:23 ` Michael Walle
2020-06-30 2:25 ` Joakim Zhang
2020-09-15 22:16 ` Marc Kleine-Budde
2020-09-16 2:26 ` Joakim Zhang
2020-09-15 22:15 ` Marc Kleine-Budde
2020-07-23 21:09 ` Michael Walle
2020-09-14 15:16 ` Michael Walle [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=64ec076a31c12218542cfa4fb081e3a7@walle.cc \
--to=michael@walle.cc \
--cc=linux-can@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.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;
as well as URLs for NNTP newsgroup(s).