From: Vincent Mailhol <mailhol@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Oliver Hartkopp" <socketcan@hartkopp.net>,
"Stéphane Grosjean" <stephane.grosjean@hms-networks.com>,
"Robert Nawrath" <mbro1689@gmail.com>,
"Minh Le" <minh.le.aj@renesas.com>,
"Duy Nguyen" <duy.nguyen.rh@renesas.com>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 07/20] can: netlink: refactor CAN_CTRLMODE_TDC_{AUTO,MANUAL} flag reset logic
Date: Tue, 23 Sep 2025 18:36:41 +0900 [thread overview]
Message-ID: <062cee74-2223-4814-bc23-647a2291aa45@kernel.org> (raw)
In-Reply-To: <20250923-bald-indigo-coati-2c3613-mkl@pengutronix.de>
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
next prev parent reply other threads:[~2025-09-23 9:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 6:03 [PATCH v2 00/20] can: netlink: preparation before introduction of CAN XL step 2/2 Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 01/20] can: dev: move struct data_bittiming_params to linux/can/bittiming.h Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 02/20] can: dev: make can_get_relative_tdco() FD agnostic and move it to bittiming.h Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 03/20] can: netlink: document which symbols are FD specific Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 04/20] can: netlink: refactor can_validate_bittiming() Vincent Mailhol
2025-09-10 6:13 ` Marc Kleine-Budde
2025-09-10 6:43 ` Vincent Mailhol
2025-09-10 10:55 ` Marc Kleine-Budde
2025-09-10 11:12 ` Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 05/20] can: netlink: add can_validate_tdc() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 06/20] can: netlink: add can_validate_databittiming() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 07/20] can: netlink: refactor CAN_CTRLMODE_TDC_{AUTO,MANUAL} flag reset logic Vincent Mailhol
2025-09-20 7:24 ` Vincent Mailhol
2025-09-22 9:43 ` Marc Kleine-Budde
2025-09-22 11:14 ` Vincent Mailhol
2025-09-22 13:06 ` Marc Kleine-Budde
2025-09-23 7:04 ` Vincent Mailhol
2025-09-23 9:08 ` Marc Kleine-Budde
2025-09-23 9:36 ` Vincent Mailhol [this message]
2025-09-10 6:03 ` [PATCH v2 08/20] can: netlink: remove useless check in can_tdc_changelink() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 09/20] can: netlink: make can_tdc_changelink() FD agnostic Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 10/20] can: netlink: add can_dtb_changelink() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 11/20] can: netlink: add can_ctrlmode_changelink() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 12/20] can: netlink: make can_tdc_get_size() FD agnostic Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 13/20] can: netlink: add can_data_bittiming_get_size() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 14/20] can: netlink: add can_bittiming_fill_info() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 15/20] can: netlink: add can_bittiming_const_fill_info() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 16/20] can: netlink: add can_bitrate_const_fill_info() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 17/20] can: netlink: make can_tdc_fill_info() FD agnostic Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 18/20] can: calc_bittiming: make can_calc_tdco() " Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 19/20] can: dev: add can_get_ctrlmode_str() Vincent Mailhol
2025-09-10 6:03 ` [PATCH v2 20/20] can: netlink: add userland error messages Vincent Mailhol
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=062cee74-2223-4814-bc23-647a2291aa45@kernel.org \
--to=mailhol@kernel.org \
--cc=duy.nguyen.rh@renesas.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbro1689@gmail.com \
--cc=minh.le.aj@renesas.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stephane.grosjean@hms-networks.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
all inboxes | Powered by JetHome®