From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Michael Riesch <michael.riesch@wolfvision.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/4] dt-bindings: add wolfvision vendor prefix
Date: Mon, 25 Mar 2024 19:32:44 +0100 [thread overview]
Message-ID: <7b1e9679-f26e-413d-9216-fd46d2874b33@linaro.org> (raw)
In-Reply-To: <20240325-feature-wolfvision-pf5-v1-1-5725445f792a@wolfvision.net>
On 25/03/2024 15:22, Michael Riesch wrote:
> Add vendor prefix for WolfVision GmbH (https://wolfvision.com).
>
> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-25 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 14:22 [PATCH 0/4] arm64: dts: rockchip: add wolfvision pf5 mainboard Michael Riesch
2024-03-25 14:22 ` [PATCH 1/4] dt-bindings: add wolfvision vendor prefix Michael Riesch
2024-03-25 18:32 ` Krzysztof Kozlowski [this message]
2024-03-25 14:22 ` [PATCH 2/4] dt-bindings: arm: rockchip: add wolfvision pf5 mainboard Michael Riesch
2024-03-25 18:33 ` Krzysztof Kozlowski
2024-03-25 14:22 ` [PATCH 3/4] arm64: dts: " Michael Riesch
2024-03-25 14:22 ` [PATCH 4/4] arm64: dts: rockchip: add wolfvision pf5 io expander board Michael Riesch
2024-03-26 17:25 ` [PATCH 0/4] arm64: dts: rockchip: add wolfvision pf5 mainboard Heiko Stuebner
2024-03-26 19:11 ` Rob Herring
2024-03-26 19:33 ` Heiko Stübner
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=7b1e9679-f26e-413d-9216-fd46d2874b33@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--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;
as well as URLs for NNTP newsgroup(s).