From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
"Charles Keepax" <ckeepax@opensource.cirrus.com>,
"Tomer Maimon" <tmaimon77@gmail.com>,
alsa-devel@alsa-project.org, linux-gpio@vger.kernel.org,
"Avi Fishman" <avifishman70@gmail.com>,
"Patrick Venture" <venture@google.com>,
openbmc@lists.ozlabs.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Tali Perry" <tali.perry1@gmail.com>,
"Richard Fitzgerald" <rf@opensource.cirrus.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
"Benjamin Fair" <benjaminfair@google.com>
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: Unify "input-debounce" schema
Date: Wed, 31 Jan 2024 09:10:31 +0100 [thread overview]
Message-ID: <CACRpkdZq4dYwJNvo1CncaHGsDeU5qQhms2SN8WGsTRwBB-Bhmw@mail.gmail.com> (raw)
In-Reply-To: <20240124190106.1540585-1-robh@kernel.org>
On Wed, Jan 24, 2024 at 8:01 PM Rob Herring <robh@kernel.org> wrote:
> nuvoton,npcm845-pinctrl defines the common "input-debounce" property as
> an array rather than an scalar. Update the common definition to expand
> it to an uint32-array, and update all the users of the property with
> array constraints.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
Patches applied, thanks for fixing this!
Yours,
Linus Walleij
prev parent reply other threads:[~2024-01-31 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 19:01 [PATCH 1/2] dt-bindings: pinctrl: Unify "input-debounce" schema Rob Herring
2024-01-24 19:01 ` [PATCH 2/2] dt-bindings: pinctrl: nuvoton,npcm845: Drop redundant type for "slew-rate" Rob Herring
2024-01-25 10:38 ` [PATCH 1/2] dt-bindings: pinctrl: Unify "input-debounce" schema Charles Keepax
2024-01-31 8:10 ` Linus Walleij [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=CACRpkdZq4dYwJNvo1CncaHGsDeU5qQhms2SN8WGsTRwBB-Bhmw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@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 read-only IMAP folder(s) and NNTP newsgroup(s).