linux-kernel - Re: [PATCH v5 03/10] dt-bindings: gpio: ast2400-gpio: Add hogs parsing

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: <CAL_JsqK1z4w62pGX0NgM7by+QRFcmBadw=CRVrvF2vv-zgAExg@mail.gmail.com>
Date: Thu, 16 Jan 2025 13:57:23 -0600
From: Rob Herring <robh@...nel.org>
To: Ninad Palsule <ninad@...ux.ibm.com>
Cc: andrew+netdev@...n.ch, pabeni@...hat.com, 
	linux-arm-kernel@...ts.infradead.org, edumazet@...gle.com, joel@....id.au, 
	krzk+dt@...nel.org, linux-kernel@...r.kernel.org, andrew@...econstruct.com.au, 
	devicetree@...r.kernel.org, davem@...emloft.net, kuba@...nel.org, 
	openipmi-developer@...ts.sourceforge.net, netdev@...r.kernel.org, 
	linux-aspeed@...ts.ozlabs.org, conor+dt@...nel.org, eajames@...ux.ibm.com, 
	minyard@....org
Subject: Re: [PATCH v5 03/10] dt-bindings: gpio: ast2400-gpio: Add hogs parsing

On Thu, Jan 16, 2025 at 9:04 AM Ninad Palsule <ninad@...ux.ibm.com> wrote:
>
> Hi Rob,
>
> On 1/14/25 17:57, Rob Herring (Arm) wrote:
> > On Tue, 14 Jan 2025 16:01:37 -0600, Ninad Palsule wrote:
> >> Allow parsing GPIO controller children nodes with GPIO hogs.
> >>
> >> Signed-off-by: Ninad Palsule <ninad@...ux.ibm.com>
> >> ---
> >>   .../devicetree/bindings/gpio/aspeed,ast2400-gpio.yaml       | 6 ++++++
> >>   1 file changed, 6 insertions(+)
> >>
> > My bot found errors running 'make dt_binding_check' on your patch:
> >
> > yamllint warnings/errors:
> >
> > dtschema/dtc warnings/errors:
> >
> >
> > doc reference errors (make refcheckdocs):
>
> I am not seeing any error even after upgrading dtschema. Also this mail
> also doesn't show any warning. Is this false negative?

I believe this happens when a prior patch in the series has an error.

Rob