From: patchwork-bot+netdevbpf@kernel.org
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: pabeni@redhat.com, kuba@kernel.org, jeroendb@google.com,
hramamurthy@google.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org,
almasrymina@google.com, bcf@google.com,
linux-kernel@vger.kernel.org, ziweixiao@google.com,
joshwash@google.com, willemb@google.com, pkaligineedi@google.com
Subject: Re: [PATCH 1/2] gve: Fix various typos and improve code comments
Date: Wed, 18 Jun 2025 01:41:08 +0000 [thread overview]
Message-ID: <175021086849.3761578.16887973997581697428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250616054504.1644770-1-alok.a.tiwari@oracle.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 15 Jun 2025 22:45:00 -0700 you wrote:
> - Correct spelling and improves the clarity of comments
> "confiugration" -> "configuration"
> "spilt" -> "split"
> "It if is 0" -> "If it is 0"
> "DQ" -> "DQO" (correct abbreviation)
> - Clarify BIT(0) flag usage in gve_get_priv_flags()
> - Replaced hardcoded array size with GVE_NUM_PTYPES
> for clarity and maintainability.
>
> [...]
Here is the summary with links:
- [1/2] gve: Fix various typos and improve code comments
https://git.kernel.org/netdev/net-next/c/b52a93bbaa51
- [2/2] gve: Return error for unknown admin queue command
https://git.kernel.org/netdev/net-next/c/b11344f63fdd
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-06-18 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 5:45 [PATCH 1/2] gve: Fix various typos and improve code comments Alok Tiwari
2025-06-16 5:45 ` [PATCH 2/2] gve: Return error for unknown admin queue command Alok Tiwari
2025-06-16 15:49 ` [PATCH 1/2] gve: Fix various typos and improve code comments Joe Damato
2025-06-16 23:25 ` Mina Almasry
2025-06-18 1:41 ` 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=175021086849.3761578.16887973997581697428.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcf@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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).