From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org,
donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] mptcp: pm: netlink: announce server-side flag
Date: Mon, 22 Sep 2025 19:00:24 +0000 [thread overview]
Message-ID: <175856762426.1122110.4750649388400694679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250919-net-next-mptcp-server-side-flag-v1-0-a97a5d561a8b@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 19 Sep 2025 14:08:57 +0200 you wrote:
> Now that the 'flags' attribute is used, it seems interesting to add one
> flag for 'server-side', a boolean value.
>
> Here are a few patches related to the 'server-side' attribute:
>
> - Patch 1: only announce this attribute on the server side.
>
> [...]
Here is the summary with links:
- [net-next,1/6] mptcp: pm: netlink: only add server-side attr when true
https://git.kernel.org/netdev/net-next/c/c9809f03c158
- [net-next,2/6] mptcp: pm: netlink: announce server-side flag
https://git.kernel.org/netdev/net-next/c/3d7ae91107b8
- [net-next,3/6] mptcp: pm: netlink: deprecate server-side attribute
https://git.kernel.org/netdev/net-next/c/c8bc168f5f3d
- [net-next,4/6] selftests: mptcp: pm: get server-side flag
https://git.kernel.org/netdev/net-next/c/e6c35529452e
- [net-next,5/6] mptcp: use _BITUL() instead of (1 << x)
https://git.kernel.org/netdev/net-next/c/5c967ebb5519
- [net-next,6/6] mptcp: remove unused returned value of check_data_fin
https://git.kernel.org/netdev/net-next/c/1be5b82c4585
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:[~2025-09-22 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 12:08 [PATCH net-next 0/6] mptcp: pm: netlink: announce server-side flag Matthieu Baerts (NGI0)
2025-09-19 12:08 ` [PATCH net-next 1/6] mptcp: pm: netlink: only add server-side attr when true Matthieu Baerts (NGI0)
2025-09-22 18:52 ` Jakub Kicinski
2025-09-19 12:08 ` [PATCH net-next 2/6] mptcp: pm: netlink: announce server-side flag Matthieu Baerts (NGI0)
2025-09-19 12:09 ` [PATCH net-next 3/6] mptcp: pm: netlink: deprecate server-side attribute Matthieu Baerts (NGI0)
2025-09-19 12:09 ` [PATCH net-next 4/6] selftests: mptcp: pm: get server-side flag Matthieu Baerts (NGI0)
2025-09-19 12:09 ` [PATCH net-next 5/6] mptcp: use _BITUL() instead of (1 << x) Matthieu Baerts (NGI0)
2025-09-19 12:09 ` [PATCH net-next 6/6] mptcp: remove unused returned value of check_data_fin Matthieu Baerts (NGI0)
2025-09-22 19: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=175856762426.1122110.4750649388400694679.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox