From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: mptcp@lists.linux.dev, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Florian Westphal <fw@strlen.de>,
Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/4] mptcp: close subflow when receiving TCP+FIN and misc.
Date: Tue, 27 Aug 2024 10:34:12 +0200 [thread overview]
Message-ID: <f22b0997-fa22-4716-a8a7-d6d8f6c49b40@kernel.org> (raw)
In-Reply-To: <20240826203308.7cc1bd5c@kernel.org>
On 27/08/2024 05:33, Jakub Kicinski wrote:
> On Mon, 26 Aug 2024 19:11:17 +0200 Matthieu Baerts (NGI0) wrote:
>> Matthieu Baerts (NGI0) (4):
>> mptcp: close subflow when receiving TCP+FIN
>> selftests: mptcp: join: cannot rm sf if closed
>> mptcp: sched: check both backup in retrans
>> mptcp: pr_debug: add missing \n at the end
>
> Why are you submitting two series to the same tree at once?
> The limit of 15 patches applies, no matter how you post.
Oh sorry, I didn't know about that.
Recently, we queued a large amount of patches targetting the -net tree,
blocking other patches queued for net-next for a few weeks now. Because
the two series I sent yesterday were not related to each others, I
thought it was OK to send them in parallel. But I understand the rate
limit. I will wait to send the next patches.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-08-27 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 17:11 [PATCH net 0/4] mptcp: close subflow when receiving TCP+FIN and misc Matthieu Baerts (NGI0)
2024-08-26 17:11 ` [PATCH net 1/4] mptcp: close subflow when receiving TCP+FIN Matthieu Baerts (NGI0)
2024-08-26 17:11 ` [PATCH net 2/4] selftests: mptcp: join: cannot rm sf if closed Matthieu Baerts (NGI0)
2024-08-26 17:11 ` [PATCH net 3/4] mptcp: sched: check both backup in retrans Matthieu Baerts (NGI0)
2024-08-26 17:11 ` [PATCH net 4/4] mptcp: pr_debug: add missing \n at the end Matthieu Baerts (NGI0)
2024-08-27 3:33 ` [PATCH net 0/4] mptcp: close subflow when receiving TCP+FIN and misc Jakub Kicinski
2024-08-27 8:34 ` Matthieu Baerts [this message]
2024-08-27 21:50 ` patchwork-bot+netdevbpf
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=f22b0997-fa22-4716-a8a7-d6d8f6c49b40@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox