[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9cfdcf56-2f47-4cfd-9fd6-2c6fa4476752@kernel.org>
Date: Mon, 22 Sep 2025 20:14:16 +0900
From: Vincent Mailhol <mailhol@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Oliver Hartkopp <socketcan@...tkopp.net>,
Stéphane Grosjean <stephane.grosjean@...-networks.com>,
Robert Nawrath <mbro1689@...il.com>, Minh Le <minh.le.aj@...esas.com>,
Duy Nguyen <duy.nguyen.rh@...esas.com>, linux-can@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 07/20] can: netlink: refactor
CAN_CTRLMODE_TDC_{AUTO,MANUAL} flag reset logic
On 22/09/2025 at 18:43, Marc Kleine-Budde wrote:
> On 20.09.2025 16:24:42, Vincent Mailhol wrote:
(...)
>> @Marc, do you think you can send your next PR to net soonish?
>>
>> I would like to rebase this series and the "rework the CAN MTU logic" series on
>> top of the MTU fix:
>>
>> https://lore.kernel.org/linux-can/20250918-can-fix-mtu-v1-0-0d1cada9393b@kernel.org/
>>
>> But to do so, I first need to wait for the MTU fix to appear on net-next and
>> there is not so much time left before the end of the development windows.
>
> This series looks fine to me. After -rc1, please check for any
> ndo_change_mtu, because the Nuvoton CAN-FD driver will go mainline, but
> not via the net-next tree.
Thanks for the head-up!
At the moment, that driver is in Lee's tree, so I was thinking of directly
preparing the fix patch and sending it to the netdev team and Lee so that both
are aware of the upcoming conflict.
I will resend my two series in the next few days as soon as the MTU fix appears
in net-next.
Yours sincerely,
Vincent Mailhol
Powered by blists - more mailing lists