[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240311091111.53191e08@kernel.org>
Date: Mon, 11 Mar 2024 09:11:11 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Simon Horman <horms@...nel.org>, Luiz Angelo Daros de Luca
<luizluca@...il.com>, Linus Walleij <linus.walleij@...aro.org>, Alvin
Šipraga <alsi@...g-olufsen.dk>, Andrew Lunn
<andrew@...n.ch>, Florian Fainelli <f.fainelli@...il.com>, Vladimir Oltean
<olteanv@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 2/4] net: dsa: realtek: keep default LED state
in rtl8366rb
On Sun, 10 Mar 2024 12:47:19 +0100 Krzysztof Kozlowski wrote:
> > FWIIW, I think this relates to review of an RFC of this patch-set.
> >
> > https://lore.kernel.org/netdev/CACRpkda8tQ2u4+jCrpOQXbBd84oW98vmiDgU+GgdYCHuZfn49A@mail.gmail.com/
>
> OK, then this is v2. RFC is state of patch, not some sort of version. Or
> just use b4 which handles this automatically...
Eh, hum. He does according to the X-Mailer header. More importantly
I thought the RFC to PATCH transition resetting version numbering
is how we always operated. Maybe b4 should be fixed?
He put the change log in the cover letter and linked to RFC, FWIW.
Powered by blists - more mailing lists