From: Vincent Mailhol <mailhol@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
"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 v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3
Date: Wed, 24 Sep 2025 02:54:36 +0900 [thread overview]
Message-ID: <715c6b6d-5672-4ba4-99d1-04fcd1dbb81b@kernel.org> (raw)
In-Reply-To: <20250923-rose-shellfish-of-wealth-c8dee7@lemur>
On 24/09/2025 at 02:08, Konstantin Ryabitsev wrote:
> On Tue, Sep 23, 2025 at 03:02:49PM +0900, Vincent Mailhol wrote:
>>> base-commit: 9b277fca90c39c8b749e659bf5c23e924c46c93b
>>> change-id: 20250831-canxl-netlink-prep-9dbf8498fd9d
>>> prerequisite-change-id: 20250915-can-fix-mtu-050a94b563a0:v2
>>> prerequisite-patch-id: 03836ed1e416f9ea221e149842cc075ac174dd3a
>>> prerequisite-patch-id: dac8f6d20f91cf996553905f08c629ca3e61d86f
>
> ...
>
>> So, when sending, I was based on Linus tree instead of net-next. I guess this is
>> why all those prerequisite-patch-id are showing up...
>
> No, I think something else went wrong here. You did list
> prerequisite-change-id, but it's only a 4-patch series. I'm not sure where the
> other ones came from. Can you push your b4 branch somewhere where I can take a
> look at it?
Thanks for jumping in this thread and volunteering to investigate. This is kind!
I pushed the v3 in my tree under the branch:
b4/misterious-prerequisite-patch-id
https://git.kernel.org/pub/scm/linux/kernel/git/mailhol/linux.git/log/?h=b4/misterious-prerequisite-patch-id
I did a 'b4 send --reflect' to double-checked that it still has the issue.
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2025-09-23 17:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 5:39 Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 01/20] can: dev: move struct data_bittiming_params to linux/can/bittiming.h Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 02/20] can: dev: make can_get_relative_tdco() FD agnostic and move it to bittiming.h Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 03/20] can: netlink: document which symbols are FD specific Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 04/20] can: netlink: refactor can_validate_bittiming() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 05/20] can: netlink: add can_validate_tdc() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 06/20] can: netlink: add can_validate_databittiming() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 07/20] can: netlink: refactor CAN_CTRLMODE_TDC_{AUTO,MANUAL} flag reset logic Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 08/20] can: netlink: remove useless check in can_tdc_changelink() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 09/20] can: netlink: make can_tdc_changelink() FD agnostic Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 10/20] can: netlink: add can_dtb_changelink() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 11/20] can: netlink: add can_ctrlmode_changelink() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 12/20] can: netlink: make can_tdc_get_size() FD agnostic Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 13/20] can: netlink: add can_data_bittiming_get_size() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 14/20] can: netlink: add can_bittiming_fill_info() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 15/20] can: netlink: add can_bittiming_const_fill_info() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 16/20] can: netlink: add can_bitrate_const_fill_info() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 17/20] can: netlink: make can_tdc_fill_info() FD agnostic Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 18/20] can: calc_bittiming: make can_calc_tdco() " Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 19/20] can: dev: add can_get_ctrlmode_str() Vincent Mailhol
2025-09-23 5:39 ` [PATCH v3 20/20] can: netlink: add userland error messages Vincent Mailhol
2025-09-23 6:02 ` [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3 Vincent Mailhol
2025-09-23 17:08 ` Konstantin Ryabitsev
2025-09-23 17:54 ` Vincent Mailhol [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=715c6b6d-5672-4ba4-99d1-04fcd1dbb81b@kernel.org \
--to=mailhol@kernel.org \
--cc=duy.nguyen.rh@renesas.com \
--cc=konstantin@linuxfoundation.org \
--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®