linux-kernel - Re: [PATCH v2 03/20] dt-bindings: Add vendor prefix for Baikal Electronics, JSC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200506192653.GA30135@ravnborg.org>
Date:   Wed, 6 May 2020 21:26:53 +0200
From:   Sam Ravnborg <sam@...nborg.org>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>
Cc:     Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Rob Herring <robh+dt@...nel.org>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Paul Burton <paulburton@...nel.org>,
        Ralf Baechle <ralf@...ux-mips.org>,
        Arnd Bergmann <arnd@...db.de>, linux-mips@...r.kernel.org,
        linux-pm@...r.kernel.org, Rob Herring <robh@...nel.org>,
        Maxime Ripard <mripard@...nel.org>,
        Heiko Stuebner <heiko.stuebner@...obroma-systems.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Stephan Gerhold <stephan@...hold.net>,
        Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 03/20] dt-bindings: Add vendor prefix for Baikal
 Electronics, JSC

Hi Sergey
> > > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> > > @@ -139,6 +139,8 @@ patternProperties:
> > >      description: Azoteq (Pty) Ltd
> > >    "^azw,.*":
> > >      description: Shenzhen AZW Technology Co., Ltd.
> > > +  "^baikal,.*":
> > > +    description: BAIKAL ELECTRONICS, JSC
> > Baikal do not use ALL UPPSECASE on their website for their name.
> > So please use same case use as they do themself.
> > 
> 
> It's not like me can't be considered as part of them.) I discussed the
> upper-case and normal version with our managers half a year ago and we
> came up to use the upper-case version. From Russian legal point of view
> it's also the upper-cased version what counts. I don't really know why
> the site use different naming, but in the internal documents it's always
> as submitted. Anyway I asked this question one more time to our managers.
> If they say to use as you suggest, then I'll resend an update in v3
> patchset, if v3 doesn't get to be necessary I'll send a followup patch
> with fix.

I had expected it was upper case because others used upper case.
But there is a good explanation and then all is fine wiht me.

And it is an alphabetic order - so
Acked-by: Sam Ravnborg <sam@...nborg.org>

> 
> -Sergey
> 
> > 
> > 	Sam
> > 
> > >    "^bananapi,.*":
> > >      description: BIPAI KEJI LIMITED
> > >    "^beacon,.*":
> > > -- 
> > > 2.25.1