From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/5] mptcp: Optimize received options handling
Date: Fri, 27 Aug 2021 09:10:27 +0000 [thread overview]
Message-ID: <163005542791.19735.1536175440276667634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210827004455.286754-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 26 Aug 2021 17:44:49 -0700 you wrote:
> These patches optimize received MPTCP option handling in terms of both
> storage and fewer conditionals to evaluate in common cases, and also add
> a couple of cleanup patches.
>
> Patches 1 and 5 do some cleanup in checksum option parsing and
> clarification of lock handling.
>
> [...]
Here is the summary with links:
- [net-next,1/5] mptcp: do not set unconditionally csum_reqd on incoming opt
https://git.kernel.org/netdev/net-next/c/8d548ea1dd15
- [net-next,2/5] mptcp: better binary layout for mptcp_options_received
https://git.kernel.org/netdev/net-next/c/a086aebae0eb
- [net-next,3/5] mptcp: consolidate in_opt sub-options fields in a bitmask
https://git.kernel.org/netdev/net-next/c/74c7dfbee3e1
- [net-next,4/5] mptcp: optimize the input options processing
https://git.kernel.org/netdev/net-next/c/f6c2ef59bcc7
- [net-next,5/5] mptcp: make the locking tx schema more readable
https://git.kernel.org/netdev/net-next/c/9758f40e90f7
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-08-27 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 0:44 [PATCH net-next 0/5] mptcp: Optimize received options handling Mat Martineau
2021-08-27 0:44 ` [PATCH net-next 1/5] mptcp: do not set unconditionally csum_reqd on incoming opt Mat Martineau
2021-08-27 0:44 ` [PATCH net-next 2/5] mptcp: better binary layout for mptcp_options_received Mat Martineau
2021-08-27 0:44 ` [PATCH net-next 3/5] mptcp: consolidate in_opt sub-options fields in a bitmask Mat Martineau
2021-08-27 0:44 ` [PATCH net-next 4/5] mptcp: optimize the input options processing Mat Martineau
2021-08-27 0:44 ` [PATCH net-next 5/5] mptcp: make the locking tx schema more readable Mat Martineau
2021-08-27 9:10 ` 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=163005542791.19735.1536175440276667634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).