All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: jjm2473 <jjm2473@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	heiko@sntech.de, quentin.schulz@cherry.de,
	kever.yang@rock-chips.com, naoki@radxa.com,
	honyuenkwun@gmail.com, inindev@gmail.com,
	ivan8215145640@gmail.com, neil.armstrong@linaro.org,
	mani@kernel.org, dsimic@manjaro.org, pbrobinson@gmail.com,
	alchark@gmail.com, jbx6244@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] arm64: dts: rockchip: introduce LinkEase EasePi R1
Date: Tue, 7 Oct 2025 17:27:47 +0100	[thread overview]
Message-ID: <aOU_g-47JEycc8ZV@shell.armlinux.org.uk> (raw)
In-Reply-To: <DD63EEOKPWNV.3IK12D6CFPTQZ@cknow.org>

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!


WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: jjm2473 <jjm2473@gmail.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	heiko@sntech.de, quentin.schulz@cherry.de,
	kever.yang@rock-chips.com, naoki@radxa.com,
	honyuenkwun@gmail.com, inindev@gmail.com,
	ivan8215145640@gmail.com, neil.armstrong@linaro.org,
	mani@kernel.org, dsimic@manjaro.org, pbrobinson@gmail.com,
	alchark@gmail.com, jbx6244@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] arm64: dts: rockchip: introduce LinkEase EasePi R1
Date: Tue, 7 Oct 2025 17:27:47 +0100	[thread overview]
Message-ID: <aOU_g-47JEycc8ZV@shell.armlinux.org.uk> (raw)
In-Reply-To: <DD63EEOKPWNV.3IK12D6CFPTQZ@cknow.org>

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!

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2025-10-07 16:28 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29  6:57 [PATCH v3 0/3] arm64: dts: rockchip: introduce LinkEase EasePi R1 Liangbin Lian
2025-09-29  6:57 ` Liangbin Lian
2025-09-29  6:57 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Document LinkEase Liangbin Lian
2025-09-29  6:57   ` Liangbin Lian
2025-09-29 12:27   ` Heiko Stuebner
2025-09-29 12:27     ` Heiko Stuebner
2025-09-29  6:57 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add LinkEase EasePi R1 Liangbin Lian
2025-09-29  6:57   ` Liangbin Lian
2025-09-29 12:28   ` Heiko Stuebner
2025-09-29 12:28     ` Heiko Stuebner
2025-09-29 18:20     ` jjm2473
2025-09-29 18:20       ` jjm2473
2025-10-06 15:43       ` Andrew Lunn
2025-10-06 15:43         ` Andrew Lunn
2025-10-07 14:56         ` jjm2473
2025-10-07 14:56           ` jjm2473
2025-09-29  6:57 ` [PATCH v3 3/3] arm64: dts: rockchip: add " Liangbin Lian
2025-09-29  6:57   ` Liangbin Lian
2025-10-06 15:51   ` Andrew Lunn
2025-10-06 15:51     ` Andrew Lunn
2025-10-07 14:32     ` jjm2473
2025-10-07 14:32       ` jjm2473
2025-10-07 14:57       ` Andrew Lunn
2025-10-07 14:57         ` Andrew Lunn
2025-10-07 16:25         ` Russell King (Oracle)
2025-10-07 16:25           ` Russell King (Oracle)
2025-10-07 16:32           ` Quentin Schulz
2025-10-07 16:32             ` Quentin Schulz
2025-10-07 17:29         ` jjm2473
2025-10-07 17:29           ` jjm2473
2025-10-07 18:32           ` Andrew Lunn
2025-10-07 18:32             ` Andrew Lunn
2025-10-09  8:47             ` Alexey Charkov
2025-10-09  8:47               ` Alexey Charkov
2025-10-09 13:04               ` Andrew Lunn
2025-10-09 13:04                 ` Andrew Lunn
2025-10-07 18:48           ` Russell King (Oracle)
2025-10-07 18:48             ` Russell King (Oracle)
2025-10-09  5:16             ` jjm2473
2025-10-09  5:16               ` jjm2473
2025-09-29 10:20 ` [PATCH v3 0/3] arm64: dts: rockchip: introduce " Diederik de Haas
2025-09-29 10:20   ` Diederik de Haas
2025-09-29 18:09   ` jjm2473
2025-09-29 18:09     ` jjm2473
2025-09-30 11:19     ` Diederik de Haas
2025-09-30 11:19       ` Diederik de Haas
2025-09-30 17:52       ` jjm2473
2025-09-30 17:52         ` jjm2473
2025-10-07 16:27       ` Russell King (Oracle) [this message]
2025-10-07 16:27         ` Russell King (Oracle)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aOU_g-47JEycc8ZV@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=honyuenkwun@gmail.com \
    --cc=inindev@gmail.com \
    --cc=ivan8215145640@gmail.com \
    --cc=jbx6244@gmail.com \
    --cc=jjm2473@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mani@kernel.org \
    --cc=naoki@radxa.com \
    --cc=neil.armstrong@linaro.org \
    --cc=pbrobinson@gmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.