From: Marek Vasut <marex@denx.de>
To: Shawn Guo <shawnguo2@yeah.net>
Cc: linux-arm-kernel@lists.infradead.org,
Rob Herring <robh@kernel.org>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Conor Dooley <conor+dt@kernel.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <festevam@gmail.com>, Jacky Bai <ping.bai@nxp.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Stefan Wahren <wahrenst@gmx.net>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
kernel@dh-electronics.com, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 01/12] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML
Date: Tue, 22 Oct 2024 13:23:42 +0200 [thread overview]
Message-ID: <d985668f-9e53-449a-9785-5cbb9b14a8fc@denx.de> (raw)
In-Reply-To: <ZxdDPSI4i/nRawlw@dragon>
On 10/22/24 8:16 AM, Shawn Guo wrote:
> On Tue, Oct 22, 2024 at 05:52:08AM +0200, Marek Vasut wrote:
>> On 10/22/24 5:25 AM, Shawn Guo wrote:
> ...
>>> I'm not sure it makes a lot sense to have "fsl,imx6ul-pinctrl: " in the
>>> subject prefix.
>> I can change it to imx-pinctrl or something and send V4 , or can you tweak
>> it while applying since the series is somewhat large ? Which do you prefer ?
>
> I expect this binding change go via pinctrl tree, so it's up to Linus.
Oh ok, so just let me know. And ideally let me know what kind of prefix
do you expect there, imx- or imx35- or ... ?
Also, what about the DT changes, do you plan to pick those or shall I
send them separately ?
next prev parent reply other threads:[~2024-10-22 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 21:11 [PATCH v3 01/12] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML Marek Vasut
2024-10-17 21:11 ` [PATCH v3 02/12] ARM: dts: imx35: Align pin config nodes with bindings Marek Vasut
2024-11-01 8:13 ` Shawn Guo
2024-10-17 21:11 ` [PATCH v3 03/12] ARM: dts: imx50: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 04/12] ARM: dts: imx51: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 05/12] ARM: dts: imx53: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 06/12] ARM: dts: imx6dl: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 07/12] ARM: dts: imx6q: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 08/12] ARM: dts: imx6qdl: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 09/12] ARM: dts: imx6qp: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 10/12] ARM: dts: imx6sl: imx6sll: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 11/12] ARM: dts: imx6sx: " Marek Vasut
2024-10-17 21:11 ` [PATCH v3 12/12] ARM: dts: imx6ul: Drop duplicate space in iomux node groups Marek Vasut
2024-10-22 3:25 ` [PATCH v3 01/12] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML Shawn Guo
2024-10-22 3:52 ` Marek Vasut
2024-10-22 6:16 ` Shawn Guo
2024-10-22 11:23 ` Marek Vasut [this message]
2024-10-22 12:55 ` Linus Walleij
2024-10-22 13:56 ` Marek Vasut
2024-10-23 9:55 ` 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=d985668f-9e53-449a-9785-5cbb9b14a8fc@denx.de \
--to=marex@denx.de \
--cc=aisheng.dong@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@dh-electronics.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo2@yeah.net \
--cc=shawnguo@kernel.org \
--cc=wahrenst@gmx.net \
/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).