From: patchwork-bot+netdevbpf@kernel.org
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH iwl-next v2 0/4] intel: fix typos in comments
Date: Thu, 10 Sep 2026 01:00:13 +0000 [thread overview]
Message-ID: <178900201362.1131357.10028347424643768946.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260907095446.27290-1-hemanth.selam@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Sep 2026 15:24:42 +0530 you wrote:
> Comment typos across the Intel ethernet drivers, split per driver. Found with scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt. Comments only, no code
> changes.
>
> v1 went out with a bare [PATCH] and a "net:" subject prefix. As
> maintainer-netdev.rst asks, v2 designates the patches to a tree, and
> each subject now names the component it touches instead of "net:". The
> series is rebased onto that tree; the diff is unchanged.
>
> [...]
Here is the summary with links:
- [iwl-next,v2,1/4] i40e: fix typos in comments
https://git.kernel.org/netdev/net-next/c/42fe5a08078f
- [iwl-next,v2,2/4] ice: fix typos in comments
https://git.kernel.org/netdev/net-next/c/e2700f56c33e
- [iwl-next,v2,3/4] ixgbevf: fix typo "enble" in comment
https://git.kernel.org/netdev/net-next/c/47ea470150c8
- [iwl-next,v2,4/4] Documentation/eth/intel: fix repeated words in comments
https://git.kernel.org/netdev/net-next/c/f3056082e084
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-09-10 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:54 Hemanth Selam
2026-09-07 9:54 ` [PATCH iwl-next v2 1/4] i40e: " Hemanth Selam
2026-09-07 9:54 ` [PATCH iwl-next v2 2/4] ice: " Hemanth Selam
2026-09-07 9:54 ` [PATCH iwl-next v2 3/4] ixgbevf: fix typo "enble" in comment Hemanth Selam
2026-09-07 9:54 ` [PATCH iwl-next v2 4/4] Documentation/eth/intel: fix repeated words in comments Hemanth Selam
2026-09-07 17:27 ` [PATCH iwl-next v2 0/4] intel: fix typos " Randy Dunlap
2026-09-08 5:46 ` Hemanth Selam
2026-09-08 5:51 ` Randy Dunlap
2026-09-08 6:00 ` Randy Dunlap
2026-09-09 21:07 ` Tony Nguyen
2026-09-10 0:50 ` Jakub Kicinski
2026-09-10 1:00 ` 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=178900201362.1131357.10028347424643768946.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hemanth.selam@gmail.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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®