From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hsun Lai <i@chainsx.cn>, robh@kernel.org
Cc: conor+dt@kernel.org, heiko@sntech.de, krzk+dt@kernel.org,
sfr@canb.auug.org.au, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add SakuraPi prefix
Date: Fri, 16 May 2025 21:48:43 +0200 [thread overview]
Message-ID: <c4eb1999-66f8-4249-b5e8-f9cbd1aa9531@kernel.org> (raw)
In-Reply-To: <20250514075914.194651-2-i@chainsx.cn>
On 14/05/2025 09:59, Hsun Lai wrote:
> Add vendor prefix for SakuraPi.org, which produces
> development boards like the SakuraPi-RK3308B.
>
> Signed-off-by: Hsun Lai <i@chainsx.cn>
> ---
>
> (no changes since v1)
>
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 3e7450c3f..744d01a76 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1299,6 +1299,8 @@ patternProperties:
> "^rve,.*":
> description: Recharge Véhicule Électrique (RVE) inc.
> "^saef,.*":
> + description: SakuraPi.org
> + "^sakurapi,.*":
> description: Saef Technology Limited
Still broken / nothing improved.
> "^samsung,.*":
> description: Samsung Semiconductor
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-16 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 7:59 [PATCH v2 0/3] Add support for Sakura Pi RK3308B Hsun Lai
2025-05-14 7:59 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add SakuraPi prefix Hsun Lai
2025-05-16 19:48 ` Krzysztof Kozlowski [this message]
2025-05-14 7:59 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add Sakura Pi RK3308B Hsun Lai
2025-05-16 19:49 ` Krzysztof Kozlowski
2025-05-14 7:59 ` [PATCH v2 3/3] arm64: dts: rockchip: add DTs for " Hsun Lai
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=c4eb1999-66f8-4249-b5e8-f9cbd1aa9531@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=i@chainsx.cn \
--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=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).