From: Jacob Keller <jacob.e.keller@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, 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>, <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: Mon, 29 Sep 2025 14:53:53 -0700 [thread overview]
Message-ID: <9a24d3d4-e8ca-4b50-9ba3-47009e00a3cc@intel.com> (raw)
In-Reply-To: <20250929115931.1d01a48b@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 604 bytes --]
On 9/29/2025 11:59 AM, Jakub Kicinski wrote:
> On Mon, 29 Sep 2025 05:44:01 -0700 Alok Tiwari 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"
>
> Hi Jake, looks trivial. Ack for us to take it directly to net-next now?
Yep, go ahead.
Acked-by: Jacob Keller <jacob.e.keller@intel.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-09-29 21:54 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 [this message]
2025-09-30 1:20 ` patchwork-bot+netdevbpf
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=9a24d3d4-e8ca-4b50-9ba3-47009e00a3cc@intel.com \
--to=jacob.e.keller@intel.com \
--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).