From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sricharan R <sricharan@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: qcom,ipq6018: Fix example 'gpio-ranges' size
Date: Thu, 25 Aug 2022 14:32:14 -0500 [thread overview]
Message-ID: <20220825193214.GA1545391-robh@kernel.org> (raw)
In-Reply-To: <CACRpkdbSycBG6ZiXfEHLquiyAMu=et81LAaGZbj38bhAccCSkw@mail.gmail.com>
On Mon, Aug 22, 2022 at 01:07:48PM +0200, Linus Walleij wrote:
> On Tue, Aug 9, 2022 at 11:46 PM Rob Herring <robh@kernel.org> wrote:
>
> > 'gpio-ranges' entries have a fixed size of 1 phandle plus arg 3 cells.
> > The qcom,ipq6018-pinctrl example is a cell short:
> >
> > Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.example.dtb: pinctrl@1000000: gpio-ranges:0: [1, 0, 80] is too short
> > From schema: /usr/local/lib/python3.10/dist-packages/dtschema/schemas/gpio/gpio.yaml
> >
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > Please ack and I can send to Linus before rc1.
>
> Sorry for delay, was on vacation :/
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> I think as binding maintainer you can just submit this kind of smaller stuff
> without any subsystem consent, if you have it acked by Krzysztof, even more so.
Don't worry, I did. It is in rc1.
Rob
prev parent reply other threads:[~2022-08-25 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 21:45 [PATCH] dt-bindings: pinctrl: qcom,ipq6018: Fix example 'gpio-ranges' size Rob Herring
2022-08-10 6:19 ` Krzysztof Kozlowski
2022-08-22 11:07 ` Linus Walleij
2022-08-25 19:32 ` Rob Herring [this message]
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=20220825193214.GA1545391-robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sricharan@codeaurora.org \
/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).