Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] net: setsockopt: fix IPV6_UNICAST_IF option for connected
 sockets
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167083981667.16910.15861355638445401606.git-patchwork-notify@kernel.org>
Date:   Mon, 12 Dec 2022 10:10:16 +0000
References: <20221208145437.GA75680@debian>
In-Reply-To: <20221208145437.GA75680@debian>
To:     Richard Gobert <richardbgobert@gmail.com>
Cc:     davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
        edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 8 Dec 2022 15:54:46 +0100 you wrote:
> Change the behaviour of ip6_datagram_connect to consider the interface
> set by the IPV6_UNICAST_IF socket option, similarly to udpv6_sendmsg.
> 
> This change is the IPv6 counterpart of the fix for IP_UNICAST_IF.
> The tests introduced by that patch showed that the incorrect
> behavior is present in IPv6 as well.
> This patch fixes the broken test.
> 
> [...]

Here is the summary with links:
  - [v2] net: setsockopt: fix IPV6_UNICAST_IF option for connected sockets
    https://git.kernel.org/netdev/net/c/526682b458b1

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