All of lore.kernel.org
 help / color / mirror / Atom feed
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/2] mptcp: Fixes for 5.17
Date: Thu, 10 Feb 2022 05:50:08 +0000	[thread overview]
Message-ID: <164447220876.5409.2789457508100360921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220210012508.226880-1-mathew.j.martineau@linux.intel.com>

Hello:

This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  9 Feb 2022 17:25:06 -0800 you wrote:
> Patch 1 fixes a MPTCP selftest bug that combined the results of two
> separate tests in the test output.
> 
> Patch 2 fixes a problem where advertised IPv6 addresses were not actually
> available for incoming MP_JOIN requests.
> 
> Kishen Maloor (1):
>   mptcp: netlink: process IPv6 addrs in creating listening sockets
> 
> [...]

Here is the summary with links:
  - [net,1/2] selftests: mptcp: add missing join check
    https://git.kernel.org/netdev/net/c/857898eb4b28
  - [net,2/2] mptcp: netlink: process IPv6 addrs in creating listening sockets
    https://git.kernel.org/netdev/net/c/029744cd4bc6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-02-10  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  1:25 [PATCH net 0/2] mptcp: Fixes for 5.17 Mat Martineau
2022-02-10  1:25 ` [PATCH net 1/2] selftests: mptcp: add missing join check Mat Martineau
2022-02-10  1:25 ` [PATCH net 2/2] mptcp: netlink: process IPv6 addrs in creating listening sockets Mat Martineau
2022-02-10  5:50 ` 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=164447220876.5409.2789457508100360921.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.