From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/5] dt-bindings: Add VeriSilicon vendor prefix
Date: Wed, 12 Feb 2025 18:01:00 +0100 [thread overview]
Message-ID: <7220a167-c321-44dc-9223-cfc6304819b3@kernel.org> (raw)
In-Reply-To: <20250212-kernel-upstreaming-add_gpio_support-v1-1-080e724a21f3@blaize.com>
On 12/02/2025 14:46, Nikolaos Pasaloukos wrote:
> VeriSilicon Microelectronics is a custom silicon service
> provider.
>
> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> ---
> 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 5079ca6ce1d1e9e2b52312439e4b1d48b262200c..14dfefbffe05180a4d8b62b3b54fc25964f56028 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -1643,6 +1643,8 @@ patternProperties:
> description: Vision Optical Technology Co., Ltd.
> "^vscom,.*":
> description: VS Visions Systems GmbH
> + "^vsi,.*":
Better verisilicon. This is supposed to match the web domain.
> + description: VeriSilicon Microelectronics Co., Ltd.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-12 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:46 [PATCH 0/5] Add support for VeriSilicon APB GPIO driver Nikolaos Pasaloukos
2025-02-12 13:46 ` [PATCH 1/5] dt-bindings: Add VeriSilicon vendor prefix Nikolaos Pasaloukos
2025-02-12 17:01 ` Krzysztof Kozlowski [this message]
2025-02-12 13:46 ` [PATCH 2/5] dt-bindings: Document VeriSilicon APB GPIO driver Nikolaos Pasaloukos
2025-02-12 17:08 ` Krzysztof Kozlowski
2025-02-12 13:46 ` [PATCH 4/5] arm64: dts: blaize-blzp1600: Add VeriSilicon GPIO support Nikolaos Pasaloukos
2025-02-12 13:46 ` [PATCH 3/5] gpio: vsiapb: Add VeriSilicon APB support Nikolaos Pasaloukos
2025-02-12 22:05 ` Linus Walleij
2025-02-12 13:46 ` [PATCH 5/5] arm64: defconfig: Add VeriSilicon GPIO driver Nikolaos Pasaloukos
2025-02-12 15:25 ` Krzysztof Kozlowski
2025-02-12 16:20 ` Nikolaos Pasaloukos
2025-02-12 16:28 ` Bartosz Golaszewski
2025-02-12 16:32 ` Nikolaos Pasaloukos
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=7220a167-c321-44dc-9223-cfc6304819b3@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@bgdev.pl \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=robh@kernel.org \
--cc=will@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