From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Bernhard Rosenkränzer" <bero@baylibre.com>, devicetree@vger.kernel.org
Cc: linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
khilman@baylibre.com
Subject: Re: [PATCH v2 4/7] dt-bindings: pinctrl: st,stm32: Deprecate pins-are-numbered
Date: Wed, 23 Nov 2022 09:18:29 +0100 [thread overview]
Message-ID: <3e7d045d-7416-d26f-1578-be83a82cc124@linaro.org> (raw)
In-Reply-To: <20221122010753.3126828-5-bero@baylibre.com>
On 22/11/2022 02:07, Bernhard Rosenkränzer wrote:
> Deprecate the pins-are-numbered property
>
> Signed-off-by: Bernhard Rosenkränzer <bero@baylibre.com>
> ---
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-23 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 1:07 [PATCH v2 0/7] Remove the pins-are-numbered DT property Bernhard Rosenkränzer
2022-11-22 1:07 ` [PATCH v2 1/7] pinctrl: mediatek: common: Remove check for pins-are-numbered Bernhard Rosenkränzer
2022-11-22 1:07 ` [PATCH v2 2/7] pinctrl: stm32: " Bernhard Rosenkränzer
2022-11-22 1:07 ` [PATCH v2 3/7] dt-bindings: pinctrl: mediatek,mt65xx: Deprecate pins-are-numbered Bernhard Rosenkränzer
2022-11-22 17:02 ` Matthias Brugger
2022-11-23 8:18 ` Krzysztof Kozlowski
2022-11-22 1:07 ` [PATCH v2 4/7] dt-bindings: pinctrl: st,stm32: " Bernhard Rosenkränzer
2022-11-22 17:03 ` Matthias Brugger
2022-11-23 8:18 ` Krzysztof Kozlowski [this message]
2022-11-22 1:07 ` [PATCH v2 5/7] arm64: dts: mediatek: Remove pins-are-numbered property Bernhard Rosenkränzer
2022-11-22 1:07 ` [PATCH v2 6/7] ARM: " Bernhard Rosenkränzer
2022-11-22 1:07 ` [PATCH v2 7/7] ARM: dts: stm32: Remove the " Bernhard Rosenkränzer
2022-11-22 17:03 ` Matthias Brugger
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=3e7d045d-7416-d26f-1578-be83a82cc124@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bero@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.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).