Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v5 net-next] net: Remove redundant calls of
 sk_tx_queue_clear().
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161198340716.22188.10513485012044993469.git-patchwork-notify@kernel.org>
Date:   Sat, 30 Jan 2021 05:10:07 +0000
References: <20210128150217.6060-1-kuniyu@amazon.co.jp>
In-Reply-To: <20210128150217.6060-1-kuniyu@amazon.co.jp>
To:     Kuniyuki Iwashima <kuniyu@amazon.co.jp>
Cc:     davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
        tariqt@nvidia.com, ttoukan.linux@gmail.com, aams@amazon.de,
        kuni1840@gmail.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, tariqt@mellanox.com,
        borisp@mellanox.com
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Fri, 29 Jan 2021 00:02:17 +0900 you wrote:
> The commit 41b14fb8724d ("net: Do not clear the sock TX queue in
> sk_set_socket()") removes sk_tx_queue_clear() from sk_set_socket() and adds
> it instead in sk_alloc() and sk_clone_lock() to fix an issue introduced in
> the commit e022f0b4a03f ("net: Introduce sk_tx_queue_mapping"). On the
> other hand, the original commit had already put sk_tx_queue_clear() in
> sk_prot_alloc(): the callee of sk_alloc() and sk_clone_lock(). Thus
> sk_tx_queue_clear() is called twice in each path.
> 
> [...]

Here is the summary with links:
  - [v5,net-next] net: Remove redundant calls of sk_tx_queue_clear().
    https://git.kernel.org/netdev/net-next/c/df610cd9163b

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