From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Raczynski <j.raczynski@samsung.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next v3] net/sun: Fix multiple typos in comments
Date: Thu, 04 Jun 2026 02:30:16 +0000 [thread overview]
Message-ID: <178054021614.2211213.3521363278754692746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260601163727.554364-1-j.raczynski@samsung.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Jun 2026 18:37:27 +0200 you wrote:
> There are some typos in comments and while they are harmless and not visible,
> there is no reason not to fix them. Fix the ones that are not register related,
> which might have intentional naming convention.
>
> Signed-off-by: Jakub Raczynski <j.raczynski@samsung.com>
> ---
> Changes in v3:
> - Just fix typos, no funny business, no changing spaces
> - Restore commit message to original
> Changes in v2:
> - Fix typo within typo fix ('empirical' word)
> - Change autoneg related sentence to make sense
> - Fix double spaces in lines where typos are fixed.
> Add annotation to commit message why only these
>
> [...]
Here is the summary with links:
- [net-next,v3] net/sun: Fix multiple typos in comments
https://git.kernel.org/netdev/net-next/c/8bcffff57d57
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-04 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260601163737eucas1p19d7a2bf830568053314738a191cbd591@eucas1p1.samsung.com>
2026-06-01 16:37 ` [PATCH net-next v3] net/sun: Fix multiple typos in comments Jakub Raczynski
2026-06-04 2:21 ` Jakub Kicinski
2026-06-04 2:30 ` patchwork-bot+netdevbpf [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=178054021614.2211213.3521363278754692746.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=j.raczynski@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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