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: [PATCHv2] SO_ZEROCOPY should return -EOPNOTSUPP rather than -ENOTSUPP
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164680681239.10719.5966093019014584969.git-patchwork-notify@kernel.org>
Date:   Wed, 09 Mar 2022 06:20:12 +0000
References: <20220307223126.djzvg44v2o2jkjsx@begin>
In-Reply-To: <20220307223126.djzvg44v2o2jkjsx@begin>
To:     Samuel Thibault <samuel.thibault@labri.fr>
Cc:     davem@davemloft.net, kuba@kernel.org,
        willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org,
        netdev@vger.kernel.org
Precedence: bulk

Hello:

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

On Mon, 7 Mar 2022 23:31:26 +0100 you wrote:
> ENOTSUPP is documented as "should never be seen by user programs",
> and thus not exposed in <errno.h>, and thus applications cannot safely
> check against it (they get "Unknown error 524" as strerror). We should
> rather return the well-known -EOPNOTSUPP.
> 
> This is similar to 2230a7ef5198 ("drop_monitor: Use correct error
> code") and 4a5cdc604b9c ("net/tls: Fix return values to avoid
> ENOTSUPP"), which did not seem to cause problems.
> 
> [...]

Here is the summary with links:
  - [PATCHv2] SO_ZEROCOPY should return -EOPNOTSUPP rather than -ENOTSUPP
    https://git.kernel.org/netdev/net-next/c/869420a8be19

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