From: patchwork-bot+netdevbpf@kernel•org
To: Xin Long <lucien.xin@gmail•com>
Cc: netdev@vger•kernel.org, stephen@networkplumber•org,
kuba@kernel•org, edumazet@google•com, pabeni@redhat•com,
dsahern@gmail•com
Subject: Re: [PATCH iproute2-next 0/2] iplink: support IPv4 BIG TCP
Date: Sat, 18 Feb 2023 17:12:33 +0000 [thread overview]
Message-ID: <167674035342.11220.11096641197731361357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1675985919.git.lucien.xin@gmail.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel•org>:
On Thu, 9 Feb 2023 18:44:22 -0500 you wrote:
> Patch 1 fixes some typos in the documents, and Patch 2 adds two
> attributes to allow userspace to enable IPv4 BIG TCP.
>
> Xin Long (2):
> iplink: fix the gso and gro max_size names in documentation
> iplink: add gso and gro max_size attributes for ipv4
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] iplink: fix the gso and gro max_size names in documentation
(no matching commit)
- [iproute2-next,2/2] iplink: add gso and gro max_size attributes for ipv4
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=1dafe448c7a2
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-02-18 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 23:44 [PATCH iproute2-next 0/2] iplink: support IPv4 BIG TCP Xin Long
2023-02-09 23:44 ` [PATCH iproute2-next 1/2] iplink: fix the gso and gro max_size names in documentation Xin Long
2023-02-09 23:44 ` [PATCH iproute2-next 2/2] iplink: add gso and gro max_size attributes for ipv4 Xin Long
2023-02-18 1:50 ` [PATCH iproute2-next 0/2] iplink: support IPv4 BIG TCP patchwork-bot+netdevbpf
2023-02-18 17:12 ` 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=167674035342.11220.11096641197731361357.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=dsahern@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lucien.xin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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