From: patchwork-bot+netdevbpf@kernel.org
To: Rushil Gupta <rushilg@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
willemb@google.com, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next v2 0/4] Add QPL mode for DQO descriptor format
Date: Sun, 06 Aug 2023 07:40:22 +0000 [thread overview]
Message-ID: <169130762217.9536.6358439352294485363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804213444.2792473-1-rushilg@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 4 Aug 2023 21:34:40 +0000 you wrote:
> GVE supports QPL ("queue-page-list") mode where
> all data is communicated through a set of pre-registered
> pages. Adding this mode to DQO.
>
> Rushil Gupta (4):
> gve: Control path for DQO-QPL
> gve: Tx path for DQO-QPL
> gve: RX path for DQO-QPL
> gve: update gve.rst
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] gve: Control path for DQO-QPL
https://git.kernel.org/netdev/net-next/c/66ce8e6b49df
- [net-next,v2,2/4] gve: Tx path for DQO-QPL
https://git.kernel.org/netdev/net-next/c/a6fb8d5a8b69
- [net-next,v2,3/4] gve: RX path for DQO-QPL
https://git.kernel.org/netdev/net-next/c/e7075ab4fb6b
- [net-next,v2,4/4] gve: update gve.rst
https://git.kernel.org/netdev/net-next/c/5a3f8d123107
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:[~2023-08-06 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 21:34 [PATCH net-next v2 0/4] Add QPL mode for DQO descriptor format Rushil Gupta
2023-08-04 21:34 ` [PATCH net-next v2 1/4] gve: Control path for DQO-QPL Rushil Gupta
2023-08-04 21:34 ` [PATCH net-next v2 2/4] gve: Tx " Rushil Gupta
2023-08-04 21:34 ` [PATCH net-next v2 3/4] gve: RX " Rushil Gupta
2023-08-04 21:34 ` [PATCH net-next v2 4/4] gve: update gve.rst Rushil Gupta
2023-08-06 7: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=169130762217.9536.6358439352294485363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rushilg@google.com \
--cc=willemb@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).