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: Wed, 24 Sep 2025 09:31:59 -0400 [thread overview]
Message-ID: <20250924-thundering-fluorescent-okapi-84a2ee@lemur> (raw)
In-Reply-To: <765d72bd-395f-462c-9c04-d2dd98244845@kernel.org>
On Wed, Sep 24, 2025 at 05:32:35PM +0900, Vincent Mailhol wrote:
> > 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
Grumble-grumble... I can't make it happen for me. I only get the expected 4
patch-ids:
base-commit: df1526752e0cd8db11b1fd4c1be3bd47409fd3ac
change-id: 20250831-canxl-netlink-prep-9dbf8498fd9d
prerequisite-change-id: 20250915-can-fix-mtu-050a94b563a0:v2
prerequisite-patch-id: 64b7803b5453bdd2ada5f2918901ad092e4ea1cf
prerequisite-patch-id: 6aecc3f1db1cd342e3b204310464179ca66b52ba
prerequisite-patch-id: 10e3a79796f2966733349c4cfcc1a61a49bc20af
prerequisite-patch-id: 5ddc3c20a99f60bddb62d58eb192facf0eb25b75
Could you run it with debug:
b4 -d send --dry-run --no-sign > /tmp/debug 2>&1
Then send me the debug file off-list?
-K
prev parent reply other threads:[~2025-09-24 13:32 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 ` [PATCH v3 00/20] can: netlink: preparation before introduction of CAN XL step 3/3 Konstantin Ryabitsev
2025-09-24 8:32 ` Vincent Mailhol
2025-09-24 13:31 ` Konstantin Ryabitsev [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=20250924-thundering-fluorescent-okapi-84a2ee@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).