From: Marek Vasut <marex@denx.de>
To: Stefan Wahren <wahrenst@gmx.net>, linux-arm-kernel@lists.infradead.org
Cc: 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>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
kernel@dh-electronics.com, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 12/12] ARM: dts: imx6ul: Align pin config nodes with bindings
Date: Thu, 17 Oct 2024 14:30:27 +0200 [thread overview]
Message-ID: <a5026879-48d9-4557-85d9-038ab73deefb@denx.de> (raw)
In-Reply-To: <aa21db7a-5b05-4529-ba75-e2111e9e6362@gmx.net>
On 10/17/24 2:14 PM, Stefan Wahren wrote:
> Hi Marek,
>
> Am 17.10.24 um 02:06 schrieb Marek Vasut:
>> Bindings expect pin configuration nodes in pinctrl to match certain
>> naming and not be part of another fake node:
>>
>> pinctrl@30330000: '...' does not match any of the regexes: 'grp$',
>> 'pinctrl-[0-9]+'
>>
>> Drop the wrapping node and adjust the names to have "grp" prefix.
>> Diff looks big but this should have no functional impact, use e.g.
>> git show -w to view the diff.
> thanks for addressing the YAML conversion, but this specific commit
> message doesn't seems to match the change?
Uh, right, commit message replaced in V3 (or shall I send this patch
separately?)
Thanks!
next prev parent reply other threads:[~2024-10-17 12:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 0:06 [PATCH v2 01/12] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML Marek Vasut
2024-10-17 0:06 ` [PATCH v2 02/12] ARM: dts: imx35: Align pin config nodes with bindings Marek Vasut
2024-10-17 0:06 ` [PATCH v2 03/12] ARM: dts: imx50: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 04/12] ARM: dts: imx51: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 05/12] ARM: dts: imx53: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 06/12] ARM: dts: imx6dl: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 07/12] ARM: dts: imx6q: " Marek Vasut
2024-10-17 6:55 ` Alexander Stein
2024-10-17 12:17 ` Marek Vasut
2024-10-17 0:06 ` [PATCH v2 08/12] ARM: dts: imx6qdl: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 09/12] ARM: dts: imx6qp: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 10/12] ARM: dts: imx6sl: imx6sll: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 11/12] ARM: dts: imx6sx: " Marek Vasut
2024-10-17 0:06 ` [PATCH v2 12/12] ARM: dts: imx6ul: " Marek Vasut
2024-10-17 12:14 ` Stefan Wahren
2024-10-17 12:30 ` Marek Vasut [this message]
2024-10-17 17:04 ` Stefan Wahren
2024-10-17 18:23 ` Marek Vasut
2024-10-17 16:26 ` [PATCH v2 01/12] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: Convert i.MX35/5x/6 to YAML Rob Herring (Arm)
2024-10-17 20:36 ` Rob Herring (Arm)
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=a5026879-48d9-4557-85d9-038ab73deefb@denx.de \
--to=marex@denx.de \
--cc=aisheng.dong@nxp.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=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