From: "André Draszik" <andre.draszik@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
devicetree@vger.kernel.org, Kees Cook <kees@kernel.org>,
linux-gpio@vger.kernel.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Will McVicker <willmcvicker@google.com>,
Conor Dooley <conor+dt@kernel.org>,
kernel-team@android.com, Bartosz Golaszewski <brgl@bgdev.pl>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: gpio: add max77759 binding
Date: Thu, 27 Feb 2025 12:56:42 +0000 [thread overview]
Message-ID: <77a8982401fdd8e986255a70e22f4fef290669cc.camel@linaro.org> (raw)
In-Reply-To: <20250227125143.GA1672649-robh@kernel.org>
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'
next prev parent reply other threads:[~2025-02-27 12:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:51 [PATCH v2 0/6] Maxim Integrated MAX77759 PMIC MFD-based drivers André Draszik
2025-02-26 17:51 ` [PATCH v2 1/6] dt-bindings: gpio: add max77759 binding André Draszik
2025-02-26 20:30 ` Rob Herring (Arm)
2025-02-27 11:19 ` André Draszik
2025-02-27 12:51 ` Rob Herring
2025-02-27 12:56 ` André Draszik [this message]
2025-02-27 13:01 ` Rob Herring (Arm)
2025-02-26 17:51 ` [PATCH v2 2/6] dt-bindings: nvmem: " André Draszik
2025-02-26 20:30 ` Rob Herring (Arm)
2025-02-27 13:05 ` Rob Herring (Arm)
2025-02-26 17:51 ` [PATCH v2 3/6] dt-bindings: mfd: " André Draszik
2025-02-27 13:04 ` Rob Herring
2025-02-27 13:13 ` André Draszik
2025-02-28 13:01 ` Rob Herring
2025-02-28 13:59 ` André Draszik
2025-02-26 17:51 ` [PATCH v2 4/6] mfd: max77759: add Maxim MAX77759 core mfd driver André Draszik
2025-02-26 17:51 ` [PATCH v2 5/6] gpio: max77759: add Maxim MAX77759 gpio driver André Draszik
2025-02-28 7:10 ` Linus Walleij
2025-02-28 10:58 ` André Draszik
2025-02-28 11:37 ` André Draszik
2025-02-26 17:51 ` [PATCH v2 6/6] nvmem: max77759: add Maxim MAX77759 NVMEM driver André Draszik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77a8982401fdd8e986255a70e22f4fef290669cc.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).