From: patchwork-bot+netdevbpf@kernel.org
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org, nktgrg@google.com,
hramamurthy@google.com, jordanrhee@google.com,
willemb@google.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
pkaligineedi@google.com, ziweixiao@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] gve: Consolidate and persist ethtool ring changes
Date: Tue, 21 Oct 2025 00:50:16 +0000 [thread overview]
Message-ID: <176100781699.473459.13729279070260421346.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251017012614.3631351-1-joshwash@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 16 Oct 2025 18:25:42 -0700 you wrote:
> From: Ankit Garg <nktgrg@google.com>
>
> Refactor the ethtool ring parameter configuration logic to address two
> issues: unnecessary queue resets and lost configuration changes when
> the interface is down.
>
> Previously, `gve_set_ringparam` could trigger multiple queue
> destructions and recreations for a single command, as different settings
> (e.g., header split, ring sizes) were applied one by one. Furthermore,
> if the interface was down, any changes made via ethtool were discarded
> instead of being saved for the next time the interface was brought up.
>
> [...]
Here is the summary with links:
- [net-next] gve: Consolidate and persist ethtool ring changes
https://git.kernel.org/netdev/net-next/c/c30fd916c4d7
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-10-21 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 1:25 [PATCH net-next] gve: Consolidate and persist ethtool ring changes Joshua Washington
2025-10-21 0:50 ` 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=176100781699.473459.13729279070260421346.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jordanrhee@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--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