[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D3FLPC79YN2S.34PAJFECP21X9@cknow.org>
Date: Wed, 14 Aug 2024 13:34:13 +0200
From: "Diederik de Haas" <didi.debian@...ow.org>
To: "Sergey 'Jin' Bostandzhyan" <jin@...iatomb.cc>,
Heiko Stübner <heiko@...ech.de>
Cc: "Daniel Golle" <daniel@...rotopia.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-rockchip@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for
FriendlyARM NanoPi R2S Plus
On Wed Aug 14, 2024 at 1:30 PM CEST, Diederik de Haas wrote:
> On Wed Aug 14, 2024 at 1:21 PM CEST, Sergey 'Jin' Bostandzhyan wrote:
> > In case you tell me to go ahead with a v3 set, should it be in this
> > thread or not? I understood RESEND's should be new, but updates should
> > stay in the thread, right?
>
> No, a new series should be its own thread too.
More correctly and hopefully more clearly:
No, a new patch version (series) should be its own thread too.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists