From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org,
geliang.tang@linux.dev, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, stable@vger.kernel.org,
syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com
Subject: Re: [PATCH net 0/2] mptcp: new reviewer and prevent a warning
Date: Wed, 03 Jan 2024 00:20:24 +0000 [thread overview]
Message-ID: <170424122489.12524.14018674920048838370.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231226-upstream-net-20231226-mptcp-prevent-warn-v1-0-1404dcc431ea@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Dec 2023 13:10:16 +0100 you wrote:
> Patch 1 adds MPTCP long time contributor -- Geliang Tang -- as a new
> reviewer for the project. Thanks!
>
> Patch 2 prevents a warning when TCP Diag is used to close internal MPTCP
> listener subflows. This is a correction for a patch introduced in v6.4
> which was fixing an issue from v5.17.
>
> [...]
Here is the summary with links:
- [net,1/2] MAINTAINERS: add Geliang as reviewer for MPTCP
https://git.kernel.org/netdev/net/c/118ba479d02c
- [net,2/2] mptcp: prevent tcp diag from closing listener subflows
https://git.kernel.org/netdev/net/c/4c0288299fd0
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:[~2024-01-03 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 12:10 [PATCH net 0/2] mptcp: new reviewer and prevent a warning Matthieu Baerts
2023-12-26 12:10 ` [PATCH net 1/2] MAINTAINERS: add Geliang as reviewer for MPTCP Matthieu Baerts
2023-12-26 12:10 ` [PATCH net 2/2] mptcp: prevent tcp diag from closing listener subflows Matthieu Baerts
2024-01-03 0: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=170424122489.12524.14018674920048838370.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@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=stable@vger.kernel.org \
--cc=syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.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 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.