From: patchwork-bot+netdevbpf@kernel•org
To: Mat Martineau <martineau@kernel•org>
Cc: matttbe@kernel•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, geliang.tang@suse•com,
kishen.maloor@intel•com, netdev@vger•kernel.org,
mptcp@lists•linux.dev, stable@vger•kernel.org
Subject: Re: [PATCH net-next 00/10] mptcp: Fixes and cleanup for v6.7
Date: Fri, 27 Oct 2023 16:20:27 +0000 [thread overview]
Message-ID: <169842362730.5811.9219746703675864811.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231025-send-net-next-20231025-v1-0-db8f25f798eb@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 25 Oct 2023 16:37:01 -0700 you wrote:
> This series includes three initial patches that we had queued in our
> mptcp-net branch, but given the likely timing of net/net-next syncs this
> week, the need to avoid introducing branch conflicts, and another batch
> of net-next patches pending in the mptcp tree, the most practical route
> is to send everything for net-next.
>
> Patches 1 & 2 fix some intermittent selftest failures by adjusting timing.
>
> [...]
Here is the summary with links:
- [net-next,01/10] selftests: mptcp: run userspace pm tests slower
https://git.kernel.org/netdev/net-next/c/f4a75e9d1100
- [net-next,02/10] selftests: mptcp: fix wait_rm_addr/sf parameters
https://git.kernel.org/netdev/net-next/c/9168ea02b898
- [net-next,03/10] mptcp: userspace pm send RM_ADDR for ID 0
https://git.kernel.org/netdev/net-next/c/84c531f54ad9
- [net-next,04/10] mptcp: drop useless ssk in pm_subflow_check_next
https://git.kernel.org/netdev/net-next/c/74cbb0c65b29
- [net-next,05/10] mptcp: use mptcp_check_fallback helper
https://git.kernel.org/netdev/net-next/c/83d580ddbe1b
- [net-next,06/10] mptcp: use mptcp_get_ext helper
https://git.kernel.org/netdev/net-next/c/a16c054b527b
- [net-next,07/10] mptcp: move sk assignment statement ahead
https://git.kernel.org/netdev/net-next/c/a6c85fc61c08
- [net-next,08/10] mptcp: define more local variables sk
https://git.kernel.org/netdev/net-next/c/14cb0e0bf39b
- [net-next,09/10] selftests: mptcp: sockopt: drop mptcp_connect var
https://git.kernel.org/netdev/net-next/c/e71aab6777a4
- [net-next,10/10] selftests: mptcp: display simult in extra_msg
https://git.kernel.org/netdev/net-next/c/629b35a225b0
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-10-27 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 23:37 [PATCH net-next 00/10] mptcp: Fixes and cleanup for v6.7 Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 01/10] selftests: mptcp: run userspace pm tests slower Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 02/10] selftests: mptcp: fix wait_rm_addr/sf parameters Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 03/10] mptcp: userspace pm send RM_ADDR for ID 0 Mat Martineau
2023-10-27 3:26 ` Jakub Kicinski
2023-10-27 15:34 ` Mat Martineau
2023-10-27 15:43 ` Jakub Kicinski
2023-10-27 15:45 ` Mat Martineau
2023-10-27 15:53 ` Jakub Kicinski
2023-10-25 23:37 ` [PATCH net-next 04/10] mptcp: drop useless ssk in pm_subflow_check_next Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 05/10] mptcp: use mptcp_check_fallback helper Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 06/10] mptcp: use mptcp_get_ext helper Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 07/10] mptcp: move sk assignment statement ahead Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 08/10] mptcp: define more local variables sk Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 09/10] selftests: mptcp: sockopt: drop mptcp_connect var Mat Martineau
2023-10-25 23:37 ` [PATCH net-next 10/10] selftests: mptcp: display simult in extra_msg Mat Martineau
2023-10-27 16:20 ` 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=169842362730.5811.9219746703675864811.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=geliang.tang@suse$(echo .)com \
--cc=kishen.maloor@intel$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=martineau@kernel$(echo .)org \
--cc=matttbe@kernel$(echo .)org \
--cc=mptcp@lists$(echo .)linux.dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=stable@vger$(echo .)kernel.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