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: <Ycnji5pNLnA/YZbX@robh.at.kernel.org>
Date:   Mon, 27 Dec 2021 12:02:19 -0400
From:   Rob Herring <robh@...nel.org>
To:     Wells Lu 呂芳騰 <wells.lu@...plus.com>
Cc:     Wells Lu <wellslutw@...il.com>,
        "dvorkin@...bo.com" <dvorkin@...bo.com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linus.walleij@...aro.org" <linus.walleij@...aro.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: pinctrl: Add dt-bindings for Sunplus
 SP7021

On Sun, Dec 26, 2021 at 12:44:25PM +0000, Wells Lu 呂芳騰 wrote:
> Hi Rob,
> 
> Thanks a lot for review.
> 
> I ran 'make dt_binding_check' and got PASS before I submitted the dt-binding doc (yaml) file.
> 
> I found the "dtschema/dtc warnings/errors:" is resulted from lack of vendor name in "vendor-prefixes.yaml".
> 
> My colleague has submitted a patch for adding our company name to the yaml file. It was acknowledged by you but not yet committed into Linux tree.
> 
> Refer to:
> 
> On Mon, 01 Nov 2021 13:01:51 +0800, Qin Jian wrote:
> > Add vendor prefix for Sunplus Technology Co., Ltd.
> > 
> > Signed-off-by: Qin Jian <qinjian@...lus1.com>
> > ---
> >  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> 
> Acked-by: Rob Herring <robh@...nel.org>
> 
> 
> Can this error be waived?

No. The patch for vendor prefix has to be applied before this one or 
we'll keep getting this error.

> When I send a new patch, should I add "vendor-prefixes.yaml"?

As it doesn't look like that series is going to make 5.17?, I can apply 
the vendor prefix patch.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ