From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, stefan@agner.ch,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 1/2] dt-bindings: gpio: fsl-imx-gpio: update gpio-ranges
Date: Tue, 28 Mar 2023 16:48:03 +0200 [thread overview]
Message-ID: <256e7c1e-c741-99f0-59e7-726c53d85c2f@linaro.org> (raw)
In-Reply-To: <CAL_JsqJvOZvw7BKYZRTf3gQwyVOmhva8BFHYF8-rf5uyo_HMUA@mail.gmail.com>
On 28/03/2023 15:57, Rob Herring wrote:
> On Tue, Mar 28, 2023 at 12:24 AM Peng Fan (OSS) <peng.fan@oss.nxp.com> wrote:
>>
>> From: Peng Fan <peng.fan@nxp.com>
>>
>> one is not enough for i.MX8, so enlarge it.
>
> But it wasn't 1, it was unbounded. As dtbs_check shows, the new bounds
> aren't right either.
Uh, so 16 is also not enough...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-28 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 5:29 [PATCH 1/2] dt-bindings: gpio: fsl-imx-gpio: update gpio-ranges Peng Fan (OSS)
2023-03-28 5:29 ` [PATCH 2/2] dt-bindings: gpio: vf610: " Peng Fan (OSS)
2023-03-28 14:45 ` Krzysztof Kozlowski
2023-03-28 14:48 ` Andrew Lunn
2023-03-29 9:21 ` Peng Fan
2023-03-29 12:14 ` Andrew Lunn
2023-03-28 12:57 ` [PATCH 1/2] dt-bindings: gpio: fsl-imx-gpio: " Rob Herring
2023-03-28 13:57 ` Rob Herring
2023-03-28 14:48 ` Krzysztof Kozlowski [this message]
2023-03-28 14:47 ` Krzysztof Kozlowski
2023-03-31 12:22 ` Linus Walleij
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=256e7c1e-c741-99f0-59e7-726c53d85c2f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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).