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] bpf: fix check against plain integer v 'NULL'
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <165790441390.797.4433680438081515423.git-patchwork-notify@kernel.org>
Date:   Fri, 15 Jul 2022 17:00:13 +0000
References: <20220714100322.260467-1-ben.dooks@sifive.com>
In-Reply-To: <20220714100322.260467-1-ben.dooks@sifive.com>
To:     Ben Dooks <ben.dooks@sifive.com>
Cc:     linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
        sudip.mukherjee@sifive.com, jude.onyenegecha@sifive.com
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 14 Jul 2022 11:03:22 +0100 you wrote:
> When checking with sparse, btf_show_type_value() is causing a
> warning about checking integer vs NULL when the macro is passed
> a pointer, due to the 'value != 0' check. Stop sparse complaining
> about any type-casting by adding a cast to the typeof(value).
> 
> This fixes the following sparse warnings:
> 
> [...]

Here is the summary with links:
  - bpf: fix check against plain integer v 'NULL'
    https://git.kernel.org/bpf/bpf-next/c/a2a5580fcbf8

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