All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gerner <thomas.gerner@muenchen-mail.de>
To: Linus Walleij <linusw@kernel.org>
Cc: Drew Fustini <fustini@kernel.org>, Guo Ren <guoren@kernel.org>,
	Fu Wei <wefu@redhat.com>,
	linux-riscv@lists.infradead.org,
	Thomas Gerner <thomas.gerner@muenchen-mail.de>
Subject: [PATCH] Re: Typo in pinctrl-th1520.c
Date: Mon, 19 Jan 2026 14:55:53 +0100	[thread overview]
Message-ID: <20260119135553.145092-1-thomas.gerner@muenchen-mail.de> (raw)
In-Reply-To: <CAD++jLkmeEoynOurZoSB_sz0XfJupiJcLPyWqbTe6fQFpYJotQ@mail.gmail.com>

On Mon, 19 Jan 2026 at 10:00:06 +0100 Linus Walleij wrote

> On Thu, Jan 15, 2026 at 8:16=E2=80=AFPM Thomas Gerner
> <thomas.gerner@muenchen-mail.de> wrote:
> 
> > I'm new in working on the Linux kernel because of my BeagleV-Ahead. Next
> > time when I send a patch I will use git send-email.
>
> Will you send a proper patch for this?
>
> Otherwise perhaps Drew can send a proper patch to fix this bug
> so I can apply it?

I hope this time the patch is proper formatted.

---
 drivers/pinctrl/pinctrl-th1520.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pinctrl/pinctrl-th1520.c b/drivers/pinctrl/pinctrl-th1520.c
index e641bad6728c..83e9c9f77370 100644
--- a/drivers/pinctrl/pinctrl-th1520.c
+++ b/drivers/pinctrl/pinctrl-th1520.c
@@ -287,7 +287,7 @@ static const struct pinctrl_pin_desc th1520_group3_pins[] = {
 	TH1520_PAD(5,  QSPI0_D0_MOSI, QSPI, PWM,  I2S,  GPIO, ____, ____, 0),
 	TH1520_PAD(6,  QSPI0_D1_MISO, QSPI, PWM,  I2S,  GPIO, ____, ____, 0),
 	TH1520_PAD(7,  QSPI0_D2_WP,   QSPI, PWM,  I2S,  GPIO, ____, ____, 0),
-	TH1520_PAD(8,  QSPI1_D3_HOLD, QSPI, ____, I2S,  GPIO, ____, ____, 0),
+	TH1520_PAD(8,  QSPI0_D3_HOLD, QSPI, ____, I2S,  GPIO, ____, ____, 0),
 	TH1520_PAD(9,  I2C2_SCL,      I2C,  UART, ____, GPIO, ____, ____, 0),
 	TH1520_PAD(10, I2C2_SDA,      I2C,  UART, ____, GPIO, ____, ____, 0),
 	TH1520_PAD(11, I2C3_SCL,      I2C,  ____, ____, GPIO, ____, ____, 0),
-- 
2.43.0

Best regards
Thomas


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-01-19 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 15:20 Typo in pinctrl-th1520.c Thomas Gerner
2026-01-15 19:03 ` Drew Fustini
2026-01-15 19:16   ` Thomas Gerner
2026-01-19  9:00     ` Linus Walleij
2026-01-19 13:55       ` Thomas Gerner [this message]
2026-01-19 14:32         ` [PATCH] " Linus Walleij
2026-01-19 15:20           ` Thomas Gerner
2026-01-20 10:10             ` Linus Walleij
2026-02-20  4:10             ` patchwork-bot+linux-riscv

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=20260119135553.145092-1-thomas.gerner@muenchen-mail.de \
    --to=thomas.gerner@muenchen-mail.de \
    --cc=fustini@kernel.org \
    --cc=guoren@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=wefu@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.