From: patchwork-bot+netdevbpf@kernel.org
To: Harshitha Ramamurthy <hramamurthy@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, pkaligineedi@google.com,
shailend@google.com, willemb@google.com, ziweixiao@google.com,
jacob.e.keller@intel.com, linux-kernel@vger.kernel.org,
almasrymina@google.com
Subject: Re: [PATCH net-next] gve: convert to use netmem for DQO RDA mode
Date: Sat, 08 Mar 2025 03:40:52 +0000 [thread overview]
Message-ID: <174140525223.2565853.15946733400929396674.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250307003905.601175-1-hramamurthy@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Mar 2025 00:39:05 +0000 you wrote:
> To add netmem support to the gve driver, add a union
> to the struct gve_rx_slot_page_info. netmem_ref is used for
> DQO queue format's raw DMA addressing(RDA) mode. The struct
> page is retained for other usecases.
>
> Then, switch to using relevant netmem helper functions for
> page pool and skb frag management.
>
> [...]
Here is the summary with links:
- [net-next] gve: convert to use netmem for DQO RDA mode
https://git.kernel.org/netdev/net-next/c/aa3e360701c3
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-03-08 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:39 [PATCH net-next] gve: convert to use netmem for DQO RDA mode Harshitha Ramamurthy
2025-03-08 3: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=174140525223.2565853.15946733400929396674.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jeroendb@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=shailend@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