[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda=zELXRSvXT98FiQh8jv9xJ3HU_Rn9iJLGzgBWmNeb+g@mail.gmail.com>
Date: Tue, 23 Jan 2024 23:02:37 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Luiz Angelo Daros de Luca <luizluca@...il.com>
Cc: netdev@...r.kernel.org, alsi@...g-olufsen.dk, andrew@...n.ch,
f.fainelli@...il.com, olteanv@...il.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
arinc.unal@...nc9.com, ansuelsmth@...il.com
Subject: Re: [PATCH 00/11] net: dsa: realtek: variants to drivers, interfaces
to a common module
On Tue, Jan 23, 2024 at 10:55 PM Luiz Angelo Daros de Luca
<luizluca@...il.com> wrote:
> Sorry for the mess. The cover-letter broke the subject-prefix I was
> using. I'll resent using the correct prefix/version.
Why not check out the "b4" tool? It helps with this kind of
stuff.
https://lore.kernel.org/netdev/CACRpkdaXV=P7NZZpS8YC67eQ2BDvR+oMzgJcjJ+GW9vFhy+3iQ@mail.gmail.com/
It's not very magical, from v4 I would create a new branch:
b4 prep -n rtl83xx -f v6.8-rc1
b4 prep --force-version 5
b4 prep --set-prefixes net-next
b4 prep --edit cover
<insert contents of patch 0/11 cover letter>
then cherry pick the 11 patches on top of that branch
and next time you b4 send it, it will pop out as v5.
OK I know it's a bit of threshold but the b4 threshold is
really low.
Yours,
Linus Walleij
Powered by blists - more mailing lists