[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aOU_g-47JEycc8ZV@shell.armlinux.org.uk>
Date: Tue, 7 Oct 2025 17:27:47 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Diederik de Haas <didi.debian@...ow.org>
Cc: jjm2473 <jjm2473@...il.com>, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, heiko@...ech.de, quentin.schulz@...rry.de,
kever.yang@...k-chips.com, naoki@...xa.com, honyuenkwun@...il.com,
inindev@...il.com, ivan8215145640@...il.com,
neil.armstrong@...aro.org, mani@...nel.org, dsimic@...jaro.org,
pbrobinson@...il.com, alchark@...il.com, jbx6244@...il.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] arm64: dts: rockchip: introduce LinkEase EasePi R1
On Tue, Sep 30, 2025 at 01:19:21PM +0200, Diederik de Haas wrote:
> On Mon Sep 29, 2025 at 8:09 PM CEST, jjm2473 wrote:
> > I have another question. If there are reviewers or co-authors later,
> > do I need to add it to the commit message and send it again?
> > Or should the reviewer or co-author add the message and
> > continue to deliver the patch?
>
> When you get a Reviewed-by tag, you should add that tag too to a new
> version. But there's no need to send a new version to just add those
> tags, the tooling used by maintainers picks those up themselves.
The only exception to this is if something changes in the patch
after the reviewed-by tag has been given - because changes mean
that the changes haven't been reviewed.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists