[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250923-rose-shellfish-of-wealth-c8dee7@lemur>
Date: Tue, 23 Sep 2025 13:08:39 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Vincent Mailhol <mailhol@...nel.org>
Cc: Marc Kleine-Budde <mkl@...gutronix.de>,
Oliver Hartkopp <socketcan@...tkopp.net>,
Stéphane Grosjean <stephane.grosjean@...-networks.com>, Robert Nawrath <mbro1689@...il.com>,
Minh Le <minh.le.aj@...esas.com>, Duy Nguyen <duy.nguyen.rh@...esas.com>,
linux-can@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/20] can: netlink: preparation before introduction
of CAN XL step 3/3
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?
-K
Powered by blists - more mailing lists