From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Vincent Mailhol <mailhol@kernel.org>
Cc: tools@kernel.org
Subject: Re: [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3
Date: Tue, 23 Sep 2025 15:50:58 -0400 [thread overview]
Message-ID: <20250923-impossible-splendid-rabbit-ba01ba@lemur> (raw)
In-Reply-To: <715c6b6d-5672-4ba4-99d1-04fcd1dbb81b@kernel.org>
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
-K
next parent reply other threads:[~2025-09-23 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250923-canxl-netlink-prep-v3-0-87a7684333f3@kernel.org>
[not found] ` <13f98eed-b535-4360-a545-0a11dbc8aa12@kernel.org>
[not found] ` <20250923-rose-shellfish-of-wealth-c8dee7@lemur>
[not found] ` <715c6b6d-5672-4ba4-99d1-04fcd1dbb81b@kernel.org>
2025-09-23 19:50 ` Konstantin Ryabitsev [this message]
2025-09-24 8:32 ` [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3 Vincent Mailhol
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=20250923-impossible-splendid-rabbit-ba01ba@lemur \
--to=konstantin@linuxfoundation.org \
--cc=mailhol@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).