From: patchwork-bot+netdevbpf@kernel.org
To: Jeroen de Borst <jeroendb@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next 0/3] gve: Add jumbo-frame support for GQ
Date: Mon, 25 Oct 2021 13:20:08 +0000 [thread overview]
Message-ID: <163516800848.2904.10878522866556441352.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211024184238.409589-1-jeroendb@google.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 24 Oct 2021 11:42:35 -0700 you wrote:
> This patchset introduces jumbo-frame support for the GQ queue format.
> The device already supports jumbo-frames on TX. This introduces
> multi-descriptor RX packets using a packet continuation bit.
>
> A widely deployed driver has a bug with causes it to fail to load
> when a MTU greater than 2048 bytes is configured. A jumbo-frame device
> option is introduced to pass a jumbo-frame MTU only to drivers that
> support it.
>
> [...]
Here is the summary with links:
- [net-next,1/3] gve: Add RX context.
https://git.kernel.org/netdev/net-next/c/1344e751e910
- [net-next,2/3] gve: Implement packet continuation for RX.
https://git.kernel.org/netdev/net-next/c/37149e9374bf
- [net-next,3/3] gve: Add a jumbo-frame device option.
https://git.kernel.org/netdev/net-next/c/255489f5b33c
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:[~2021-10-25 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 18:42 [PATCH net-next 0/3] gve: Add jumbo-frame support for GQ Jeroen de Borst
2021-10-24 18:42 ` [PATCH net-next 1/3] gve: Add RX context Jeroen de Borst
2021-10-24 18:42 ` [PATCH net-next 2/3] gve: Implement packet continuation for RX Jeroen de Borst
2021-10-24 18:42 ` [PATCH net-next 3/3] gve: Add a jumbo-frame device option Jeroen de Borst
2021-10-25 13:20 ` 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=163516800848.2904.10878522866556441352.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jeroendb@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).