linux-kernel - Re: [PATCH v2 07/20] can: netlink: refactor CAN_CTRLMODE_TDC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <062cee74-2223-4814-bc23-647a2291aa45@kernel.org>
Date: Tue, 23 Sep 2025 18:36:41 +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 23/09/2025 at 18:08, Marc Kleine-Budde wrote:
> On 23.09.2025 16:04:41, Vincent Mailhol wrote:
>>>> I will resend my two series in the next few days as soon as the MTU fix appears
>>>> in net-next.
>>>
>>> I don't know how much time we have between the merge of net into
>>> net-next and the acceptance of the last PR by the network team for the
>>> next merge window. We will see.
>>
>> With the pull request to net/main being delayed, I decided to finally remove the
>> patch which was in conflict and send the rest:
>>
>> https://lore.kernel.org/linux-can/20250923-can-fix-mtu-v3-0-581bde113f52@kernel.org/
>>
>> and:
>>
>> https://lore.kernel.org/linux-can/20250923-canxl-netlink-prep-v4-0-e720d28f66fe@kernel.org/
>>
>> These are my last two series for this development window (to be applied in order).
>>
>> Also, sorry for the noise when sending those twice.
> 
> I've merged both series to linux-can-next. Thanks. b4 was a bit
> confused, it took the canxl-netlink-prep when asked to merge the
> can-fix-mtu series and it added the prerequisite patches when merging
> canxl-netlink-prep on top of can-fix-mtu.

Yeh, I also had a lot of trouble on my side as you could see. This is the first
time I deal with such a complex series, at least, I am happy it is now merge.

> My next net-next PR is prepared as linux-can-next-for-6.18-20250923. Can
> you check if I took the correct patches?

I just checked, everything is there and my WIP CAN XL patches rebase nicely on
top. All good, thanks!


Yours sincerely,
Vincent Mailhol