From: patchwork-bot+netdevbpf@kernel.org
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org, hramamurthy@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com,
sdf@fomichev.me, willemb@google.com, pkaligineedi@google.com,
ziweixiao@google.com, jfraker@google.com, linux@treblig.org,
nktgrg@google.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] gve: Improve RX buffer length management
Date: Tue, 11 Nov 2025 01:40:29 +0000 [thread overview]
Message-ID: <176282522924.2843765.11992898311639277599.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251106192746.243525-1-joshwash@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Nov 2025 11:27:42 -0800 you wrote:
> From: Ankit Garg <nktgrg@google.com>
>
> This patch series improves the management of the RX buffer length for
> the DQO queue format in the gve driver. The goal is to make RX buffer
> length config more explicit, easy to change, and performant by default.
>
> We accomplish that in four patches:
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] gve: Decouple header split from RX buffer length
https://git.kernel.org/netdev/net-next/c/40fef85ceb9c
- [net-next,v3,2/4] gve: Use extack to log xdp config verification errors
https://git.kernel.org/netdev/net-next/c/091a3b6ff2b9
- [net-next,v3,3/4] gve: Allow ethtool to configure rx_buf_len
https://git.kernel.org/netdev/net-next/c/d235bb213f41
- [net-next,v3,4/4] gve: Default to max_rx_buffer_size for DQO if device supported
https://git.kernel.org/netdev/net-next/c/09a81a0f4fb7
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-11-11 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 19:27 [PATCH net-next v3 0/4] gve: Improve RX buffer length management joshwash
2025-11-06 19:27 ` [PATCH net-next v3 1/4] gve: Decouple header split from RX buffer length joshwash
2025-11-06 19:27 ` [PATCH net-next v3 2/4] gve: Use extack to log xdp config verification errors joshwash
2025-11-06 19:27 ` [PATCH net-next v3 3/4] gve: Allow ethtool to configure rx_buf_len joshwash
2025-11-06 19:27 ` [PATCH net-next v3 4/4] gve: Default to max_rx_buffer_size for DQO if device supported joshwash
2025-11-11 1:40 ` 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=176282522924.2843765.11992898311639277599.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=hramamurthy@google.com \
--cc=jfraker@google.com \
--cc=john.fastabend@gmail.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=netdev@vger.kernel.org \
--cc=nktgrg@google.com \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=sdf@fomichev.me \
--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