From: Vincent Mailhol <mailhol@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Pavel Pisa <pisa@fel.cvut.cz>,
Ondrej Ille <ondrej.ille@gmail.com>,
linux-can@vger.kernel.org,
David Laight <david.laight.linux@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Andrea Daoud <andreadaoud6@gmail.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Jiri Novak <jnovak@fel.cvut.cz>
Subject: Re: [PATCH v2] can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit.
Date: Fri, 9 Jan 2026 11:50:42 +0100 [thread overview]
Message-ID: <25616e3d-9fd9-491e-9a93-fa48d3e7ba2c@kernel.org> (raw)
In-Reply-To: <20260109-robust-clay-falcon-2f3ecb-mkl@pengutronix.de>
On 09/01/2026 at 10:29, Marc Kleine-Budde wrote:
> On 06.01.2026 23:14:47, Vincent Mailhol wrote:
>>> thanks for pointing to Transmission Delay Compensation
>>> related code introduced in 5.16 kernel. I have noticed it
>>> in the past but not considered it yet and I think
>>> that we need minimal fixes to help users and
>>> allow change to propagate into stable series now.
>
> How to proceed. Take this fix now an (hopefully) port to the mainline
> TDC framework later?
While I would definitely prefer to see the TDC framework implementation
rather than this quick fix, I will also not block it.
If you feel confident to continue with that patch, go ahead.
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2026-01-09 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 11:16 [PATCH v2] can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit Pavel Pisa
2026-01-05 12:49 ` Marc Kleine-Budde
2026-01-05 20:27 ` Vincent Mailhol
2026-01-06 0:53 ` Pavel Pisa
2026-01-06 22:14 ` Vincent Mailhol
2026-01-09 9:29 ` Marc Kleine-Budde
2026-01-09 10:50 ` Vincent Mailhol [this message]
2026-01-09 10:56 ` Marc Kleine-Budde
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=25616e3d-9fd9-491e-9a93-fa48d3e7ba2c@kernel.org \
--to=mailhol@kernel.org \
--cc=andreadaoud6@gmail.com \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=jnovak@fel.cvut.cz \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--cc=pabeni@redhat.com \
--cc=pisa@fel.cvut.cz \
--cc=wg@grandegger.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