From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: at91-vinco: Fix "status" values
Date: Tue, 18 Jul 2023 18:37:22 +0200 [thread overview]
Message-ID: <31e4da6a-44ab-5c0a-ae32-c0fcf09d7cb8@microchip.com> (raw)
In-Reply-To: <20230626221010.3946263-1-robh@kernel.org>
On 27/06/2023 at 00:10, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The defined value for "status" is "disabled", not "disable".
>
> Signed-off-by: Rob Herring <robh@kernel.org>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
We'll queue the patch in our tree (and linux-next) soon (tm).
Best regards,
Nicolas
> ---
> arch/arm/boot/dts/microchip/at91-vinco.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/microchip/at91-vinco.dts b/arch/arm/boot/dts/microchip/at91-vinco.dts
> index ebeaa6ab500e..ecbdacf48708 100644
> --- a/arch/arm/boot/dts/microchip/at91-vinco.dts
> +++ b/arch/arm/boot/dts/microchip/at91-vinco.dts
> @@ -159,7 +159,7 @@ usb0: gadget@400000 {
> atmel,vbus-gpio = <&pioE 31 GPIO_ACTIVE_HIGH>;
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_usba_vbus>;
> - status = "disable";
> + status = "disabled";
> };
>
> usb1: ohci@500000 {
> @@ -168,7 +168,7 @@ usb1: ohci@500000 {
> &pioE 11 GPIO_ACTIVE_LOW
> &pioE 12 GPIO_ACTIVE_LOW
> >;
> - status = "disable";
> + status = "disabled";
> };
>
> usb2: ehci@600000 {
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-07-18 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 22:10 Rob Herring
2023-07-18 16:22 ` Rob Herring
2023-07-18 16:37 ` Nicolas Ferre [this message]
2023-08-02 4:48 ` claudiu beznea
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=31e4da6a-44ab-5c0a-ae32-c0fcf09d7cb8@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®