From: "Diederik de Haas" <didi.debian@cknow.org>
To: "jjm2473" <jjm2473@gmail.com>
Cc: <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, 30 Sep 2025 13:19:21 +0200 [thread overview]
Message-ID: <DD63EEOKPWNV.3IK12D6CFPTQZ@cknow.org> (raw)
In-Reply-To: <CAP_9mL6+uoeG7LX8YCcUFjoU13De1CdPFqxNNfoJvOdsOrYo5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2882 bytes --]
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.
If you 'just' get review comments, then you'd usually just
improve the patch and you could reference it in a changelog item (to
indicate you addressed it, ttboyk).
If you think a reviewer helped you 'significantly', you could choose to
add an Helped-by tag, but whether you think someone deserves some
credits that way, is up to you(r judgement).
(Co-)authors are usually known upon first submission. If you later find
out that that list was incorrect/incomplete, then you would add
Co-developed-by + Signed-off-by tags on a new version.
HTH,
Diederik
> Diederik de Haas <didi.debian@cknow.org> 于2025年9月29日周一 18:20写道:
>>
>> On Mon Sep 29, 2025 at 8:57 AM CEST, Liangbin Lian wrote:
>> > LinkEase EasePi R1 [1] is a high-performance mini router.
>> > ...
>> > [1] https://doc.linkease.com/zh/guide/easepi-r1/hardware.html
>> >
>> > Signed-off-by: Liangbin Lian <jjm2473@gmail.com>
>> > ---
>> >
>> > Changes in v2:
>> > - Change deprecated "rockchip,system-power-controller" to "system-power-controller"
>> > - Link to v1: https://lore.kernel.org/r/20250925055906.83375-1-jjm2473@gmail.com/
>>
>> You received an Acked-by on patch 1 and 2 in v1 of this patch set.
>> You're supposed to add that to the next/new version(s) or explain why
>> you choose not to do that (bc f.e. there was a major change, but that
>> does not seem applicable to those patches).
>>
>> Cheers,
>> Diederik
>>
>> > Changes in v3:
>> > - Fix typo ('status = "disable"' -> 'status = "disabled"') found by kernel test robot https://lore.kernel.org/all/202509261328.Grjhp029-lkp@intel.com/
>> > - Link to v2: https://lore.kernel.org/r/20250925092037.13582-1-jjm2473@gmail.com/
>> >
>> > ---
>> >
>> > Liangbin Lian (3):
>> > dt-bindings: vendor-prefixes: Document LinkEase
>> > dt-bindings: arm: rockchip: Add LinkEase EasePi R1
>> > arm64: dts: rockchip: add LinkEase EasePi R1
>> >
>> > .../devicetree/bindings/arm/rockchip.yaml | 5 +
>> > .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>> > arch/arm64/boot/dts/rockchip/Makefile | 1 +
>> > .../boot/dts/rockchip/rk3568-easepi-r1.dts | 692 ++++++++++++++++++
>> > 4 files changed, 700 insertions(+)
>> > create mode 100644 arch/arm64/boot/dts/rockchip/rk3568-easepi-r1.dts
>> >
>> >
>> > base-commit: d0ca0df179c4b21e2a6c4a4fb637aa8fa14575cb
>>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-30 11:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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 12:28 ` Heiko Stuebner
2025-09-29 18:20 ` jjm2473
2025-10-06 15:43 ` Andrew Lunn
2025-10-07 14:56 ` jjm2473
2025-09-29 6:57 ` [PATCH v3 3/3] arm64: dts: rockchip: add " Liangbin Lian
2025-10-06 15:51 ` Andrew Lunn
2025-10-07 14:32 ` jjm2473
2025-10-07 14:57 ` Andrew Lunn
2025-10-07 16:25 ` Russell King (Oracle)
2025-10-07 16:32 ` Quentin Schulz
2025-10-07 17:29 ` jjm2473
2025-10-07 18:32 ` Andrew Lunn
2025-10-09 8:47 ` Alexey Charkov
2025-10-09 13:04 ` Andrew Lunn
2025-10-07 18:48 ` Russell King (Oracle)
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 18:09 ` jjm2473
2025-09-30 11:19 ` Diederik de Haas [this message]
2025-09-30 17:52 ` jjm2473
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=DD63EEOKPWNV.3IK12D6CFPTQZ@cknow.org \
--to=didi.debian@cknow.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome