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] inode: Remove second initialization of the bpf_preload_lock
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161774638114.15399.8001840751538307402.git-patchwork-notify@kernel.org>
Date:   Tue, 06 Apr 2021 21:59:41 +0000
References: <20210405194904.GA148013@LEGION>
In-Reply-To: <20210405194904.GA148013@LEGION>
To:     Muhammad Usama Anjum <musamaanjum@gmail.com>
Cc:     ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
        kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
        john.fastabend@gmail.com, kpsingh@kernel.org,
        netdev@vger.kernel.org, bpf@vger.kernel.org,
        linux-kernel@vger.kernel.org, zhengyongjun3@huawei.com,
        dan.carpenter@oracle.com
Precedence: bulk

Hello:

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

On Tue, 6 Apr 2021 00:49:04 +0500 you wrote:
> bpf_preload_lock is already defined with DEFINE_MUTEX. There is no need
> to initialize it again. Remove the extraneous initialization.
> 
> Signed-off-by: Muhammad Usama Anjum <musamaanjum@gmail.com>
> ---
>  kernel/bpf/inode.c | 2 --
>  1 file changed, 2 deletions(-)

Here is the summary with links:
  - inode: Remove second initialization of the bpf_preload_lock
    https://git.kernel.org/bpf/bpf-next/c/957dca3df624

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