From: Wei Xu <xuwei5@hisilicon.com>
To: Tony Lindgren <tony@atomide.com>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Dinh Nguyen <dinguyen@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
Niravkumar L Rabara <niravkumar.l.rabara@intel.com>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: Change pinconf controller node name to pinctrl
Date: Wed, 7 Jun 2023 09:47:59 +0800 [thread overview]
Message-ID: <647FE1CF.3000504@hisilicon.com> (raw)
In-Reply-To: <20230510103816.39015-1-tony@atomide.com>
Hi Tony,
On 2023/5/10 18:38, Tony Lindgren wrote:
> According to the pinctrl binding pinmux and pinctrl are valid controller
> names. Let's replace pinconf with pinctrl so we don't get new warnings
> when pinctrl-singl yaml binding gets merged.
>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Dinh Nguyen <dinguyen@kernel.org>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
> Cc: Ray Jui <rjui@broadcom.com>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Scott Branden <sbranden@broadcom.com>
> Cc: Wei Xu <xuwei5@hisilicon.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
Acked-by: Wei Xu <xuwei5@hisilicon.com> #hisilicon
Thanks!
Best Regards,
Wei
prev parent reply other threads:[~2023-06-07 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 10:38 [PATCH] arm64: dts: Change pinconf controller node name to pinctrl Tony Lindgren
2023-05-10 10:51 ` Krzysztof Kozlowski
2023-05-10 10:53 ` Tony Lindgren
2023-05-10 12:10 ` Krzysztof Kozlowski
2023-06-13 22:40 ` Dinh Nguyen
2023-05-18 22:56 ` Florian Fainelli
2023-06-07 1:47 ` Wei Xu [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=647FE1CF.3000504@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=niravkumar.l.rabara@intel.com \
--cc=olof@lixom.net \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=tony@atomide.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).