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,
pabeni@redhat.com, edumazet@google.com, kishen.maloor@intel.com,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net 0/2] mptcp: Disconnect and selftest fixes
Date: Mon, 11 Jul 2022 11:00:13 +0000 [thread overview]
Message-ID: <165753721328.18044.8546633791151784612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220708233610.410786-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 8 Jul 2022 16:36:08 -0700 you wrote:
> Patch 1 switches to a safe list iterator in the MPTCP disconnect code.
>
> Patch 2 adds the userspace_pm.sh selftest script to the MPTCP selftest
> Makefile, resolving the netdev/check_selftest CI failure.
>
> Matthieu Baerts (1):
> selftests: mptcp: validate userspace PM tests by default
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: fix subflow traversal at disconnect time
https://git.kernel.org/netdev/net/c/5c835bb142d4
- [net,2/2] selftests: mptcp: validate userspace PM tests by default
https://git.kernel.org/netdev/net/c/3ddabc433670
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-07-11 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 23:36 [PATCH net 0/2] mptcp: Disconnect and selftest fixes Mat Martineau
2022-07-08 23:36 ` [PATCH net 1/2] mptcp: fix subflow traversal at disconnect time Mat Martineau
2022-07-08 23:36 ` [PATCH net 2/2] selftests: mptcp: validate userspace PM tests by default Mat Martineau
2022-07-11 11: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=165753721328.18044.8546633791151784612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kishen.maloor@intel.com \
--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).