[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa71b888-e55b-a57d-28cc-f1a583e615f9@kernel.org>
Date: Fri, 27 Oct 2023 08:34:27 -0700 (PDT)
From: Mat Martineau <martineau@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
cc: Matthieu Baerts <matttbe@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Geliang Tang <geliang.tang@...e.com>,
Kishen Maloor <kishen.maloor@...el.com>, netdev@...r.kernel.org,
mptcp@...ts.linux.dev
Subject: Re: [PATCH net-next 03/10] mptcp: userspace pm send RM_ADDR for ID
0
On Thu, 26 Oct 2023, Jakub Kicinski wrote:
> On Wed, 25 Oct 2023 16:37:04 -0700 Mat Martineau wrote:
>> Fixes: d9a4594edabf ("mptcp: netlink: Add MPTCP_PM_CMD_REMOVE")
>> Cc: stable@...r.kernel.org
>
> CC: stable@ + net-next really doesn't make sense.
> Either it's important or it's not. Which one do you pick?
>
Hi Jakub -
This is what I was attempting to explain in the cover letter:
> 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.
So, that's the reasoning, but I'll send v2 without the cc's.
- Mat
Powered by blists - more mailing lists