Add vendor prefix for Huawei (https://www.huawei.com/en/)

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,.*":
-- 
2.25.1

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,.*":

On Mon, Jan 10, 2022 at 09:55:43AM +0000, Jonathan Cameron wrote:
> 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?

Not sure about bindings, but there are device trees using the huawei 
vendor prefix. I'm aware of at least these two:
/arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts
/arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts

Similar situation with the other vendor prefix patches I've sent yesterday.

Should I send a v2 with an updated patch description for this and
the other patches?

Thanks,

Stanislav

> 
> 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,.*":
> 

On Mon, Jan 10, 2022 at 01:13:07PM +0100, Stanislav Jakubek wrote:
> On Mon, Jan 10, 2022 at 09:55:43AM +0000, Jonathan Cameron wrote:
> > 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?
> 
> Not sure about bindings, but there are device trees using the huawei 
> vendor prefix. I'm aware of at least these two:
> /arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts
> /arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
> 
> Similar situation with the other vendor prefix patches I've sent yesterday.
> 
> Should I send a v2 with an updated patch description for this and
> the other patches?

Yes.

Rob