[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f22b0997-fa22-4716-a8a7-d6d8f6c49b40@kernel.org>
Date: Tue, 27 Aug 2024 10:34:12 +0200
From: Matthieu Baerts <matttbe@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: mptcp@...ts.linux.dev, Mat Martineau <martineau@...nel.org>,
Geliang Tang <geliang@...nel.org>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Florian Westphal <fw@...len.de>, Shuah Khan <shuah@...nel.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH net 0/4] mptcp: close subflow when receiving TCP+FIN and
misc.
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.
Powered by blists - more mailing lists