From: patchwork-bot+netdevbpf@kernel.org
To: Jiangshan Yi <13667453960@163.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
bpf@vger.kernel.org, haoluo@google.com, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, eddyz87@gmail.com,
sdf@fomichev.me, danieltimlee@gmail.com,
linux-kernel@vger.kernel.org, yijiangshan@kylinos.cn,
wangqiang1@kylinos.cn
Subject: Re: [PATCH] samples/bpf: fix compilation errors with cf-protection option
Date: Thu, 15 Aug 2024 23:00:37 +0000 [thread overview]
Message-ID: <172376283799.3058964.8728018764972507383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240815135524.140675-1-13667453960@163.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 15 Aug 2024 21:55:24 +0800 you wrote:
> From: Jiangshan Yi <yijiangshan@kylinos.cn>
>
> Currently, compiling the bpf programs will result the compilation errors
> with the cf-protection option as follows in arm64 and loongarch64 machine
> when using gcc 12.3.1 and clang 17.0.6. This commit fixes the compilation
> errors by limited the cf-protection option only used in x86 platform.
>
> [...]
Here is the summary with links:
- samples/bpf: fix compilation errors with cf-protection option
https://git.kernel.org/bpf/bpf-next/c/fdf1c728fac5
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:[~2024-08-15 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 13:55 [PATCH] samples/bpf: fix compilation errors with cf-protection option Jiangshan Yi
2024-08-15 23:00 ` 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=172376283799.3058964.8728018764972507383.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=13667453960@163.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=danieltimlee@gmail.com \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=wangqiang1@kylinos.cn \
--cc=yijiangshan@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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