From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 00355D530; Fri, 27 Oct 2023 15:43:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Iwa5h2i0" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 093DBC433C8; Fri, 27 Oct 2023 15:43:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1698421407; bh=fW1iwSQjrGUOgKahb2I9wionUD0d03M3iNVyFD4+qUw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Iwa5h2i0SUwKbH3CXWxfZdjkPJgSe9FB14y77dpheQk4DnKrzCwZglkv96JtfV1GT WH/eTsJ+y3CoAurbQXV8YIfYu207jMWmIj9vXrNwgWh1r3jMAIYiolvcOMS6mr9OuT TQTV6Qwkrxg0zlPT5T52JpRfGsEXk/LPvMixYoiFnldrANanNpo3DhEMlT8E22qwsw lQsYH2GUFYvg+XdNgjBP3DZ9jU9WmaP2bmxV94RtDS186XX5YFDPKnIOZqmk+ywcci MUnQDsPorVfA+cMxIqehKFpg2AuZsr5a8mQKuDIpJUW+liHfDLBTRtIsS4Fe2rwB3P UTxQNeE1hWTkg== Date: Fri, 27 Oct 2023 08:43:24 -0700 From: Jakub Kicinski To: Mat Martineau Cc: Matthieu Baerts , "David S. Miller" , Eric Dumazet , Paolo Abeni , Geliang Tang , Kishen Maloor , netdev@vger.kernel.org, mptcp@lists.linux.dev Subject: Re: [PATCH net-next 03/10] mptcp: userspace pm send RM_ADDR for ID 0 Message-ID: <20231027084324.42e434bb@kernel.org> In-Reply-To: References: <20231025-send-net-next-20231025-v1-0-db8f25f798eb@kernel.org> <20231025-send-net-next-20231025-v1-3-db8f25f798eb@kernel.org> <20231026202629.07ecc7a7@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 27 Oct 2023 08:34:27 -0700 (PDT) Mat Martineau wrote: > > 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. No need, I can strip when applying.