Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] libbpf: add pr_warn() for EINVAL cases in
 linker_sanity_check_elf
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <170208482423.18108.3043597727814423980.git-patchwork-notify@kernel.org>
Date:   Sat, 09 Dec 2023 01:20:24 +0000
References: <20231208215100.435876-1-slyich@gmail.com>
In-Reply-To: <20231208215100.435876-1-slyich@gmail.com>
To:     Sergei Trofimovich <slyich@gmail.com>
Cc:     bpf@vger.kernel.org, eddyz87@gmail.com,
        linux-kernel@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
        yonghong.song@linux.dev, john.fastabend@gmail.com,
        kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
        jolsa@kernel.org
Precedence: bulk

Hello:

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

On Fri,  8 Dec 2023 21:51:00 +0000 you wrote:
> Before the change on `i686-linux` `systemd` build failed as:
> 
>     $ bpftool gen object src/core/bpf/socket_bind/socket-bind.bpf.o src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o
>     Error: failed to link 'src/core/bpf/socket_bind/socket-bind.bpf.unstripped.o': Invalid argument (22)
> 
> After the change it fails as:
> 
> [...]

Here is the summary with links:
  - [v2] libbpf: add pr_warn() for EINVAL cases in linker_sanity_check_elf
    https://git.kernel.org/bpf/bpf-next/c/32fa05839862

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