Received-SPF: pass (google.com: domain of linux-kernel+bounces-110572-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 1/1] libbpf: Define MFD_CLOEXEC if not available
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171104702707.24409.2393183534870190384.git-patchwork-notify@kernel.org>
Date: Thu, 21 Mar 2024 18:50:27 +0000
References: <ZfxZ9nCyKvwmpKkE@x1>
In-Reply-To: <ZfxZ9nCyKvwmpKkE@x1>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: andrii@kernel.org, daniel@iogearbox.net, bpf@vger.kernel.org,
 linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org

Hello:

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

On Thu, 21 Mar 2024 13:01:58 -0300 you wrote:
> Since its going directly to the syscall to avoid not having
> memfd_create() available in some systems, do the same for its
> MFD_CLOEXEC flags, defining it if not available.
> 
> This fixes the build in those systems, noticed while building perf on a
> set of build containers.
> 
> [...]

Here is the summary with links:
  - [1/1] libbpf: Define MFD_CLOEXEC if not available
    https://git.kernel.org/bpf/bpf/c/ddb2ffdc474a

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