From: Vincent Mailhol <mailhol@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3
Date: Wed, 24 Sep 2025 17:32:35 +0900 [thread overview]
Message-ID: <765d72bd-395f-462c-9c04-d2dd98244845@kernel.org> (raw)
In-Reply-To: <20250923-impossible-splendid-rabbit-ba01ba@lemur>
On 24/09/2025 at 04:50, Konstantin Ryabitsev wrote:
> On Wed, Sep 24, 2025 at 02:54:36AM +0900, Vincent Mailhol wrote:
>>> 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.
>
> Dropping others for now, and just adding the tools list.
>
> What is your net-next/main pointing at right now?
>
> git rev-parse net-next/main
$ git rev-parse net-next/main
df1526752e0cd8db11b1fd4c1be3bd47409fd3ac
Also, just in case:
$ b4 --version
0.14.2
(which is my distro's latest version).
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2025-09-24 8:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 5:39 [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3 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
2025-09-23 19:50 ` Konstantin Ryabitsev
2025-09-24 8:32 ` Vincent Mailhol [this message]
2025-09-24 13:31 ` Konstantin Ryabitsev
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=765d72bd-395f-462c-9c04-d2dd98244845@kernel.org \
--to=mailhol@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.