public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
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
Subject: Re: [PATCH 1/1] libbpf: Define MFD_CLOEXEC if not available
Date: Thu, 21 Mar 2024 18:50:27 +0000	[thread overview]
Message-ID: <171104702707.24409.2393183534870190384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZfxZ9nCyKvwmpKkE@x1>

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



      parent reply	other threads:[~2024-03-21 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 16:01 [PATCH 1/1] libbpf: Define MFD_CLOEXEC if not available Arnaldo Carvalho de Melo
2024-03-21 16:13 ` Andrii Nakryiko
2024-03-21 16:16   ` Arnaldo Carvalho de Melo
2024-03-21 18:50 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171104702707.24409.2393183534870190384.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox