From: patchwork-bot+netdevbpf@kernel.org
To: Alok Tiwari <alok.a.tiwari@oracle.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, netdev@vger.kernel.org,
horms@kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next] ixgbe: fix typos and docstring inconsistencies
Date: Tue, 30 Sep 2025 01:20:55 +0000 [thread overview]
Message-ID: <175919525524.1775912.18040158539252294729.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250929124427.79219-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 29 Sep 2025 05:44:01 -0700 you wrote:
> Corrected function and variable name typos in comments and docstrings:
> ixgbe_write_ee_hostif_X550 -> ixgbe_write_ee_hostif_data_X550
> ixgbe_get_lcd_x550em -> ixgbe_get_lcd_t_x550em
> "Determime" -> "Determine"
> "point to hardware structure" -> "pointer to hardware structure"
> "To turn on the LED" -> "To turn off the LED"
>
> [...]
Here is the summary with links:
- [net-next] ixgbe: fix typos and docstring inconsistencies
https://git.kernel.org/netdev/net-next/c/96ccc93744f8
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:[~2025-09-30 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 12:44 [PATCH net-next] ixgbe: fix typos and docstring inconsistencies Alok Tiwari
2025-09-29 12:49 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-09-29 12:52 ` Paul Menzel
2025-09-29 18:59 ` Jakub Kicinski
2025-09-29 21:53 ` Jacob Keller
2025-09-30 1:20 ` 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=175919525524.1775912.18040158539252294729.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 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).