From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: soc@kernel.org, linux-omap@vger.kernel.org,
Peter Vasil <petervasil@gmail.com>
Subject: Re: [PATCH] ARM: omap2: Fix copy/paste bug
Date: Wed, 14 Jun 2023 14:15:54 +0300 [thread overview]
Message-ID: <20230614111554.GJ14287@atomide.com> (raw)
In-Reply-To: <20230614093032.403982-1-linus.walleij@linaro.org>
* Linus Walleij <linus.walleij@linaro.org> [230614 12:30]:
> I mistyped one of the SD/MMC GPIO lines on the Nokia n810 which
> was supposed to be "vio" as "vsd".
>
> Fix it up.
>
> Reported-by: Peter Vasil <petervasil@gmail.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> SoC maintainers: please apply this directly where the rest of the
> OMAP clean-ups are.
Reviewed-by: Tony Lindgren <tony@atomide.com>
> arch/arm/mach-omap2/board-n8x0.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap2/board-n8x0.c b/arch/arm/mach-omap2/board-n8x0.c
> index 564bf80a2621..8e3b5068d4ab 100644
> --- a/arch/arm/mach-omap2/board-n8x0.c
> +++ b/arch/arm/mach-omap2/board-n8x0.c
> @@ -158,7 +158,7 @@ static struct gpiod_lookup_table nokia810_mmc_gpio_table = {
> "vsd", 1, GPIO_ACTIVE_HIGH),
> /* Slot index 1, VIO power, GPIO 9 */
> GPIO_LOOKUP_IDX("gpio-0-15", 9,
> - "vsd", 1, GPIO_ACTIVE_HIGH),
> + "vio", 1, GPIO_ACTIVE_HIGH),
> { }
> },
> };
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-06-14 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 9:30 [PATCH] ARM: omap2: Fix copy/paste bug Linus Walleij
2023-06-14 11:15 ` Tony Lindgren [this message]
2023-06-22 16:10 ` patchwork-bot+linux-soc
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=20230614111554.GJ14287@atomide.com \
--to=tony@atomide.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=petervasil@gmail.com \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).