Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] libbpf: Fix determine_ptr_size() guessing
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <165403741330.9645.14080630675434689339.git-patchwork-notify@kernel.org>
Date:   Tue, 31 May 2022 22:50:13 +0000
References: <20220524094447.332186-1-douglas.raillard@arm.com>
In-Reply-To: <20220524094447.332186-1-douglas.raillard@arm.com>
To:     Douglas RAILLARD <douglas.raillard@arm.com>
Cc:     bpf@vger.kernel.org, beata.michalska@arm.com, 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, nathan@kernel.org, ndesaulniers@google.com,
        trix@redhat.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Precedence: bulk

Hello:

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

On Tue, 24 May 2022 10:44:47 +0100 you wrote:
> From: Douglas Raillard <douglas.raillard@arm.com>
> 
> One strategy employed by libbpf to guess the pointer size is by finding
> the size of "unsigned long" type. This is achieved by looking for a type
> of with the expected name and checking its size.
> 
> Unfortunately, the C syntax is friendlier to humans than to computers
> as there is some variety in how such a type can be named. Specifically,
> gcc and clang do not use the same names for integer types in debug info:
> 
> [...]

Here is the summary with links:
  - [v3] libbpf: Fix determine_ptr_size() guessing
    https://git.kernel.org/bpf/bpf-next/c/8a140f1b12f7

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