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
Subject: Re: [PATCH net 0/3] mptcp: A few fixes
Date: Fri, 21 Jan 2022 06:00:13 +0000 [thread overview]
Message-ID: <164274481358.1814.10002816263958082331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220121003529.54930-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 20 Jan 2022 16:35:26 -0800 you wrote:
> Here are some fixes from the mptcp tree:
>
> Patch 1 fixes a RCU locking issue when processing a netlink command that
> updates endpoint flags in the in-kernel MPTCP path manager.
>
> Patch 2 fixes a typo affecting available endpoint id tracking.
>
> [...]
Here is the summary with links:
- [net,1/3] mptcp: fix msk traversal in mptcp_nl_cmd_set_flags()
https://git.kernel.org/netdev/net/c/8e9eacad7ec7
- [net,2/3] mptcp: fix removing ids bitmap setting
https://git.kernel.org/netdev/net/c/a4c0214fbee9
- [net,3/3] selftests: mptcp: fix ipv6 routing setup
https://git.kernel.org/netdev/net/c/9846921dba49
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:[~2022-01-21 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 0:35 [PATCH net 0/3] mptcp: A few fixes Mat Martineau
2022-01-21 0:35 ` [PATCH net 1/3] mptcp: fix msk traversal in mptcp_nl_cmd_set_flags() Mat Martineau
2022-01-21 0:35 ` [PATCH net 2/3] mptcp: fix removing ids bitmap setting Mat Martineau
2022-01-21 0:35 ` [PATCH net 3/3] selftests: mptcp: fix ipv6 routing setup Mat Martineau
2022-01-21 6:00 ` 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=164274481358.1814.10002816263958082331.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 \
/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.