Received-SPF: pass (google.com: domain of linux-kernel+bounces-178123-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next] tcp: socket option to check for MPTCP fallback to
 TCP
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171563763083.31066.11558902540602032643.git-patchwork-notify@kernel.org>
Date: Mon, 13 May 2024 22:00:30 +0000
References: <20240509-upstream-net-next-20240509-mptcp-tcp_is_mptcp-v1-1-f846df999202@kernel.org>
In-Reply-To: <20240509-upstream-net-next-20240509-mptcp-tcp_is_mptcp-v1-1-f846df999202@kernel.org>
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, edumazet@google.com, davem@davemloft.net,
 dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com, martineau@kernel.org,
 geliang@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 09 May 2024 20:10:10 +0200 you wrote:
> A way for an application to know if an MPTCP connection fell back to TCP
> is to use getsockopt(MPTCP_INFO) and look for errors. The issue with
> this technique is that the same errors -- EOPNOTSUPP (IPv4) and
> ENOPROTOOPT (IPv6) -- are returned if there was a fallback, *or* if the
> kernel doesn't support this socket option. The userspace then has to
> look at the kernel version to understand what the errors mean.
> 
> [...]

Here is the summary with links:
  - [net-next] tcp: socket option to check for MPTCP fallback to TCP
    https://git.kernel.org/netdev/net-next/c/c084ebd77a00

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html