From: Josua Mayer <josua@solid-run.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linusw@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benjamin Bara <benjamin.bara@skidata.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Jon Nettleton <jon@solid-run.com>,
Mikhail Anikin <mikhail.anikin@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v4 2/7] dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Allow input-enable pinconf
Date: Fri, 4 Sep 2026 11:14:02 +0000 [thread overview]
Message-ID: <c0a37ff2-b133-4bd9-82c6-732f58e2c5ec@solid-run.com> (raw)
In-Reply-To: <CAMuHMdUE3+qBdy2CoSQMzJ1iePiv0PSTfOjxHAqgp78i_XpMPQ@mail.gmail.com>
Hi Geert,
Am 04.09.26 um 12:12 schrieb Geert Uytterhoeven:
> Hi Joshua,
>
> On Thu, 3 Sept 2026 at 11:23, Josua Mayer <josua@solid-run.com> wrote:
>> Am 02.09.26 um 14:58 schrieb Linus Walleij:
>>> On Wed, Sep 2, 2026 at 1:50 PM Josua Mayer <josua@solid-run.com> wrote:
>>>> The list of allowed pinconf properties already includes input-enable,
>>>> but has omitted input-disable.
>>>>
>>>> Both refer to the same hardware property, setting and clearing input-enable.
>>>>
>>>> Add input-disable to the list.
>>>>
>>>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>>> (...)
>>>> + input-disable: true
>>> The Subject of this patch is "Allow input-enable pinconf".
>>>
>>> But what you are doing is allowing input-disable.
>>>
>>> With the subject fixed:
>>> Reviewed-by: Linus Walleij <linusw@kernel.org>
>> Thanks!
>> I'll fix the subject ... !
>>
>> ("dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Allow input-disable pinconf")
> No need to resend, I will fix this while applying
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-pinctrl for v7.4.
>
> I will also add "output-disable", which is missing, too.
Thanks!
However I am ready to send v8. If I drop it my series will fail dtbs_check.
Is it okay if I do resend it, and/or should I wait and cherry-pick your
version
so that it is easily dropped while applying without conflict?
Or drop it and live with failing dtbs_check?
next prev parent reply other threads:[~2026-09-04 11:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 11:50 [PATCH v4 0/7] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Josua Mayer
2026-09-02 11:50 ` [PATCH v4 1/7] dt-bindings: soc: " Josua Mayer
2026-09-02 11:50 ` [PATCH v4 2/7] dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Allow input-enable pinconf Josua Mayer
2026-09-02 12:58 ` Linus Walleij
2026-09-03 9:23 ` Josua Mayer
2026-09-04 10:12 ` Geert Uytterhoeven
2026-09-04 11:14 ` Josua Mayer [this message]
2026-09-04 11:16 ` Geert Uytterhoeven
2026-09-04 11:33 ` Josua Mayer
2026-09-02 11:50 ` [PATCH v4 3/7] dt-bindings: usb: cypress,hx3: make peer-hub property optional Josua Mayer
2026-09-02 11:50 ` [PATCH v4 4/7] arm64: dts: renesas: add support for solidrun rzg2l som and hb-iiot evb Josua Mayer
2026-09-02 11:50 ` [PATCH v4 5/7] arm64: dts: renesas: add support for solidrun rzv2l " Josua Mayer
2026-09-02 11:50 ` [PATCH v4 6/7] arm64: dts: renesas: add support for solidrun rzg2lc " Josua Mayer
2026-09-02 12:03 ` sashiko-bot
2026-09-02 11:50 ` [PATCH v4 7/7] arm64: dts: renesas: rzg2l(c)/rzv2l hb-iiot: add dsi panel dt overlay Josua Mayer
2026-09-02 11:59 ` sashiko-bot
2026-09-03 10:06 ` Josua Mayer
2026-09-02 12:03 ` [PATCH v4 0/7] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Geert Uytterhoeven
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=c0a37ff2-b133-4bd9-82c6-732f58e2c5ec@solid-run.com \
--to=josua@solid-run.com \
--cc=benjamin.bara@skidata.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jon@solid-run.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mikhail.anikin@solid-run.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=yazan.shhady@solid-run.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