From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: David Heidelberg <david@ixit.cz>, Roger Quadros <rogerq@ti.com>,
devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, Wei Xu <xuwei5@hisilicon.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: add second HiSilicon prefix
Date: Tue, 22 Feb 2022 16:02:19 -0600 [thread overview]
Message-ID: <YhVda7zSwd+DYkc2@robh.at.kernel.org> (raw)
In-Reply-To: <20220221082228.34407-1-krzysztof.kozlowski@canonical.com>
On Mon, 21 Feb 2022 09:22:26 +0100, Krzysztof Kozlowski wrote:
> There are few boards DTS using "hisi,rst-syscon" property -
> undocumented "hisi" prefix. The property will not be changed in DTS to
> non-deprecated one, because of compatibility reasons. Add deprecated
> "hisi" prefix to silence DT schema warnings.
>
> Cc: Wei Xu <xuwei5@hisilicon.com>
> Cc: David Heidelberg <david@ixit.cz>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>
> ---
>
> See:
> https://lore.kernel.org/all/61AF1E3B.5060706@hisilicon.com/
> https://www.spinics.net/lists/arm-kernel/msg887577.html
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Applied, thanks!
prev parent reply other threads:[~2022-02-22 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 8:22 [PATCH 1/3] dt-bindings: vendor-prefixes: add second HiSilicon prefix Krzysztof Kozlowski
2022-02-21 8:22 ` [PATCH 2/3] dt-bindings: vendor-prefixes: add second Synopsys prefix Krzysztof Kozlowski
2022-02-22 22:02 ` Rob Herring
2022-02-21 8:22 ` [PATCH 3/3] dt-bindings: usb: do not use deprecated synopsys prefix Krzysztof Kozlowski
2022-02-22 22:02 ` Rob Herring
2022-02-21 20:13 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add second HiSilicon prefix David Heidelberg
2022-02-22 7:08 ` Wei Xu
2022-02-22 22:02 ` Rob Herring [this message]
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=YhVda7zSwd+DYkc2@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=xuwei5@hisilicon.com \
/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).