[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77a8982401fdd8e986255a70e22f4fef290669cc.camel@linaro.org>
Date: Thu, 27 Feb 2025 12:56:42 +0000
From: André Draszik <andre.draszik@...aro.org>
To: Rob Herring <robh@...nel.org>
Cc: "Gustavo A. R. Silva" <gustavoars@...nel.org>,
devicetree@...r.kernel.org, Kees Cook <kees@...nel.org>,
linux-gpio@...r.kernel.org, Srinivas Kandagatla
<srinivas.kandagatla@...aro.org>, Tudor Ambarus <tudor.ambarus@...aro.org>,
Will McVicker <willmcvicker@...gle.com>, Conor Dooley
<conor+dt@...nel.org>, kernel-team@...roid.com, Bartosz Golaszewski
<brgl@...ev.pl>, linux-hardening@...r.kernel.org,
linux-kernel@...r.kernel.org, Lee Jones <lee@...nel.org>, Peter Griffin
<peter.griffin@...aro.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: gpio: add max77759 binding
On Thu, 2025-02-27 at 06:51 -0600, Rob Herring wrote:
> On Thu, Feb 27, 2025 at 11:19:55AM +0000, André Draszik wrote:
>
> > The error is because the binding's 'description:' references the
> > mfd binding using the complete path and the mfd binding is added
> > in a later patch only in this version of the series:
> >
> > > ... For additional information, see
> > > Documentation/devicetree/bindings/mfd/maxim,max77759.yaml.
> >
> > the error goes away if a relative path is used instead:
> >
> > > ... For additional information, see
> > > ../mfd/maxim,max77759.yaml.
>
> No, just ignore the error. I believe it gets fixed with the mfd binding
> applied. I'm not too concerned if refcheckdocs is bisectable.
Thanks Rob, and yes, it does go away then.
Cheers,
Andre'
Powered by blists - more mailing lists