From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, kafai@fb.com, andrii@kernel.org,
songliubraving@fb.com, haoluo@google.com, yhs@fb.com,
ast@kernel.org, daniel@iogearbox.net, kpsingh@kernel.org,
davem@davemloft.net, kuba@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Use sys_pidfd_open() helper when possible
Date: Thu, 13 Oct 2022 19:20:14 +0000 [thread overview]
Message-ID: <166568881480.839.9685292948102950876.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221011071249.3471760-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 11 Oct 2022 15:12:49 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> SYS_pidfd_open may be undefined for old glibc, so using sys_pidfd_open()
> helper defined in task_local_storage_helpers.h instead to fix potential
> build failure.
>
> And according to commit 7615d9e1780e ("arch: wire-up pidfd_open()"), the
> syscall number of pidfd_open is always 434 except for alpha architure,
> so update the definition of __NR_pidfd_open accordingly.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Use sys_pidfd_open() helper when possible
https://git.kernel.org/bpf/bpf-next/c/62c69e89e81b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-13 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 7:12 [PATCH bpf-next] selftests/bpf: Use sys_pidfd_open() helper when possible Hou Tao
2022-10-13 19:20 ` 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=166568881480.839.9685292948102950876.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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