mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Conor Dooley <conor@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Michael Zhu <michael.zhu@starfivetech.com>,
	Drew Fustini <drew@beagleboard.org>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	devicetree@vger.kernel.org, Icenowy Zheng <uwu@icenowy.me>
Subject: Re: [PATCH v3 1/2] dt-bindings: riscv: starfive: add xunlong,orangepi-rv
Date: Mon, 24 Nov 2025 13:59:05 -0800	[thread overview]
Message-ID: <0e851ca0-1f56-437d-ae14-094c114d3b77@freeshell.de> (raw)
In-Reply-To: <20251124-state-campsite-3e7788a495c1@spud>


On 11/24/25 05:22, Conor Dooley wrote:
> On Mon, Nov 24, 2025 at 08:28:10AM +0100, Krzysztof Kozlowski wrote:
>> On Sun, Nov 23, 2025 at 02:50:44PM -0800, E Shattow wrote:
>>> From: Icenowy Zheng <uwu@icenowy.me>
>>>
>>> Add "xunlong,orangepi-rv" as a StarFive JH7110 SoC-based board.
>>>
>>> Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
>>> Signed-off-by: E Shattow <e@freeshell.de>
>>
>> <form letter>
>> This is a friendly reminder during the review process.
>>
>> It looks like you received a tag and forgot to add it.
> 
> It's from me, don't resubmit just to add it since it'll be me applying
> anyway.
> 

Hi Conor,

Okay. Yes I'd dropped the tag since the commit message is appreciably
different, and you would be handling it again anyways. Thanks! And thank
you Krzysztof for the reminder -E

>>
>> If you do not know the process, here is a short explanation:
>> Please add Acked-by/Reviewed-by/Tested-by tags when posting new
>> versions of patchset, under or above your Signed-off-by tag, unless
>> patch changed significantly (e.g. new properties added to the DT
>> bindings). Tag is "received", when provided in a message replied to you
>> on the mailing list. Tools like b4 can help here. However, there's no
>> need to repost patches *only* to add the tags. The upstream maintainer
>> will do that for tags received on the version they apply.
>>
>> Please read:
>> https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
>>
>> If a tag was not added on purpose, please state why and what changed.
>> </form letter>


  reply	other threads:[~2025-11-24 21:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 22:50 [PATCH v3 0/2] riscv: dts: starfive: Add OrangePi RV board E Shattow
2025-11-23 22:50 ` [PATCH v3 1/2] dt-bindings: riscv: starfive: add xunlong,orangepi-rv E Shattow
2025-11-24  7:28   ` Krzysztof Kozlowski
2025-11-24 13:22     ` Conor Dooley
2025-11-24 21:59       ` E Shattow [this message]
2025-11-25  7:28         ` Krzysztof Kozlowski
2025-11-25  7:33           ` Icenowy Zheng
2025-11-25  7:48             ` Krzysztof Kozlowski
2025-11-25  8:01               ` Icenowy Zheng
2025-11-25 13:07                 ` E Shattow
2025-11-25 19:14                   ` Conor Dooley
2025-11-26 20:34                     ` E Shattow
2025-11-26  8:23                   ` Krzysztof Kozlowski
2025-11-23 22:50 ` [PATCH v3 2/2] riscv: dts: starfive: add Orange Pi RV E Shattow
2025-11-24 11:07   ` Conor Dooley
2025-11-24 11:08     ` Icenowy Zheng
2025-11-24 13:21       ` Conor Dooley
2025-11-24 21:56         ` E Shattow
2025-11-25 22:24 ` [PATCH v3 0/2] riscv: dts: starfive: Add OrangePi RV board Conor Dooley
2025-11-26 13:48   ` Emil Renner Berthing

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=0e851ca0-1f56-437d-ae14-094c114d3b77@freeshell.de \
    --to=e@freeshell.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.zhu@starfivetech.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=uwu@icenowy.me \
    /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

all inboxes | Powered by JetHome®