From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
marcelo.leitner@gmail.com, nhorman@tuxdriver.com,
davem@davemloft.net, kuba@kernel.org, martin.varghese@nokia.com,
alexander.duyck@gmail.com
Subject: Re: [PATCH net-next 0/3] net: make udp tunnel devices support fraglist
Date: Tue, 19 Jan 2021 04:30:09 +0000 [thread overview]
Message-ID: <161103060919.4335.7926202532790955178.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1610704037.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 15 Jan 2021 17:47:44 +0800 you wrote:
> Like GRE device, UDP tunnel devices should also support fraglist, so
> that some protocol (like SCTP) HW GSO that requires NETIF_F_FRAGLIST
> in the dev can work. Especially when the lower device support both
> NETIF_F_GSO_UDP_TUNNEL and NETIF_F_GSO_SCTP.
>
> Xin Long (3):
> vxlan: add NETIF_F_FRAGLIST flag for dev features
> geneve: add NETIF_F_FRAGLIST flag for dev features
> bareudp: add NETIF_F_FRAGLIST flag for dev features
>
> [...]
Here is the summary with links:
- [net-next,1/3] vxlan: add NETIF_F_FRAGLIST flag for dev features
https://git.kernel.org/netdev/net-next/c/cb2c57112432
- [net-next,2/3] geneve: add NETIF_F_FRAGLIST flag for dev features
https://git.kernel.org/netdev/net-next/c/18423e1a9d7d
- [net-next,3/3] bareudp: add NETIF_F_FRAGLIST flag for dev features
https://git.kernel.org/netdev/net-next/c/3224dcfd850f
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-01-19 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 9:47 [PATCH net-next 0/3] net: make udp tunnel devices support fraglist Xin Long
2021-01-15 9:47 ` [PATCH net-next 1/3] vxlan: add NETIF_F_FRAGLIST flag for dev features Xin Long
2021-01-15 9:47 ` [PATCH net-next 2/3] geneve: " Xin Long
2021-01-15 9:47 ` [PATCH net-next 3/3] bareudp: " Xin Long
2021-01-19 4:30 ` 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=161103060919.4335.7926202532790955178.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.