From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: add Huawei
Date: Mon, 10 Jan 2022 09:55:43 +0000 [thread overview]
Message-ID: <20220110095543.00001ac0@Huawei.com> (raw)
In-Reply-To: <20220109132311.GA2827@standask-GA-A55M-S2HP>
On Sun, 9 Jan 2022 14:23:11 +0100
Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
> Add vendor prefix for Huawei (https://www.huawei.com/en/)
Patch description should say why... Is there an existing binding
using a huawei vendor prefix?
Thanks,
Jonathan
>
> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.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 a13d6a19c2b4..18ffa2d7379f 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -515,6 +515,8 @@ patternProperties:
> description: HannStar Display Co.
> "^holtek,.*":
> description: Holtek Semiconductor, Inc.
> + "^huawei,.*":
> + description: Huawei Technologies Co., Ltd.
> "^hugsun,.*":
> description: Shenzhen Hugsun Technology Co. Ltd.
> "^hwacom,.*":
next prev parent reply other threads:[~2022-01-10 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 13:23 [PATCH] dt-bindings: vendor-prefixes: add Huawei Stanislav Jakubek
2022-01-10 9:55 ` Jonathan Cameron [this message]
2022-01-10 12:13 ` Stanislav Jakubek
2022-01-12 2:14 ` Rob Herring
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=20220110095543.00001ac0@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stano.jakubek@gmail.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).