All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Thomas Gerner <thomas.gerner@muenchen-mail.de>
Cc: linux-riscv@lists.infradead.org, linusw@kernel.org,
	fustini@kernel.org, guoren@kernel.org, wefu@redhat.com
Subject: Re: [PATCH] Re: Typo in pinctrl-th1520.c
Date: Fri, 20 Feb 2026 04:10:58 +0000	[thread overview]
Message-ID: <177156065829.189817.12382540253108472501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119152004.166749-1-thomas.gerner@muenchen-mail.de>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Linus Walleij <linusw@kernel.org>:

On Mon, 19 Jan 2026 16:20:02 +0100 you wrote:
> On 19.01.26 at 15:32 Linus Walleij wrote:
> > On Mon, Jan 19, 2026 at 2:56 PM Thomas Gerner
> > <thomas.gerner@muenchen-mail.de> wrote:
> >> On Mon, 19 Jan 2026 at 10:00:06 +0100 Linus Walleij wrote
> >>
> >>> On Thu, Jan 15, 2026 at 8:16 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.
> >
> > Nah it doesn't work... but I could fix that up if you send it again
> > and provide your "Signed-off-by" because otherwise I cannot legally
> > apply it.
> >
> 
> [...]

Here is the summary with links:
  - Re: Typo in pinctrl-th1520.c
    https://git.kernel.org/riscv/c/304c3ebcaff3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

      parent reply	other threads:[~2026-02-20  4:11 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       ` [PATCH] " Thomas Gerner
2026-01-19 14:32         ` 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 [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=177156065829.189817.12382540253108472501.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=fustini@kernel.org \
    --cc=guoren@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=thomas.gerner@muenchen-mail.de \
    --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.