From: Coia Prant <coiaprant@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Dragan Simic <dsimic@manjaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add graperain
Date: Wed, 01 Jul 2026 18:01:30 +0800 [thread overview]
Message-ID: <A4CA0393-B348-48A0-B5DB-D1F9098EB37B@gmail.com> (raw)
In-Reply-To: <20260701-sturdy-imported-oryx-dfc12a@quoll>
On July 1, 2026 3:05:45 PM GMT+08:00, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>On Tue, Jun 30, 2026 at 11:38:09PM +0800, Coia Prant wrote:
>> Add graperain to the vendor prefixes.
>>
>> Link: https://www.graperain.cn/ (China)
>> Link: https://www.graperain.com/ (Global)
>>
>> Signed-off-by: Coia Prant <coiaprant@gmail.com>
>> ---
>> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>
><form letter>
>This is a friendly reminder during the review process.
>
>It looks like you received a tag and forgot to add it.
>
>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 in the patch changelog
>or cover letter why and what changed.
></form letter>
>
>Best regards,
>Krzysztof
>
My apologies! I am quite new to the kernel submission process and
missed picking up the tag from v1.
Since I need to spin a v3 anyway to fix the text wrapping issue in
patch 2, I will make sure to include the missing tags and resend the
entire series.
Thanks for your patience and for pointing this out!
Best,
Coia
next prev parent reply other threads:[~2026-07-09 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 15:38 [PATCH v2 0/3] Add devicetree for the Graperain G3568 v2 Coia Prant
2026-06-30 15:38 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add graperain Coia Prant
2026-07-01 7:05 ` Krzysztof Kozlowski
2026-07-01 10:01 ` Coia Prant [this message]
2026-06-30 15:38 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add Graperain G3568 series Coia Prant
2026-07-01 7:07 ` Krzysztof Kozlowski
2026-07-01 9:57 ` Coia Prant
2026-06-30 15:38 ` [PATCH v2 3/3] arm64: dts: rockchip: Add devicetree for the Graperain G3568 v2 Coia Prant
2026-06-30 15:52 ` sashiko-bot
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=A4CA0393-B348-48A0-B5DB-D1F9098EB37B@gmail.com \
--to=coiaprant@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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