public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, puranjay@kernel.org,
	xukuohai@huaweicloud.com, catalin.marinas@arm.com,
	will@kernel.org, shuah@kernel.org, menglong8.dong@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v5 0/3] bpf, arm64: Add fsession support
Date: Sat, 31 Jan 2026 22:00:17 +0000	[thread overview]
Message-ID: <176989681714.6968.8564830272874377531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260131144950.16294-1-leon.hwang@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sat, 31 Jan 2026 22:49:47 +0800 you wrote:
> Similar to commit 98770bd4e6df ("bpf,x86: add fsession support for x86_64"),
> add fsession support on arm64.
> 
> Patch #1 adds bpf_jit_supports_fsession() to prevent fsession loading
> on architectures that do not implement fsession support.
> 
> Patch #2 implements fsession support in the arm64 BPF JIT trampoline.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/3] bpf: Add bpf_jit_supports_fsession()
    https://git.kernel.org/bpf/bpf-next/c/8798902f2b8b
  - [bpf-next,v5,2/3] bpf, arm64: Add fsession support
    https://git.kernel.org/bpf/bpf-next/c/e3aa56b3ac17
  - [bpf-next,v5,3/3] selftests/bpf: Enable get_func_args and get_func_ip tests on arm64
    https://git.kernel.org/bpf/bpf-next/c/7f10da2133b1

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




      parent reply	other threads:[~2026-01-31 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 14:49 [PATCH bpf-next v5 0/3] bpf, arm64: Add fsession support Leon Hwang
2026-01-31 14:49 ` [PATCH bpf-next v5 1/3] bpf: Add bpf_jit_supports_fsession() Leon Hwang
2026-01-31 14:49 ` [PATCH bpf-next v5 2/3] bpf, arm64: Add fsession support Leon Hwang
2026-01-31 14:49 ` [PATCH bpf-next v5 3/3] selftests/bpf: Enable get_func_args and get_func_ip tests on arm64 Leon Hwang
2026-01-31 22: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=176989681714.6968.8564830272874377531.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=catalin.marinas@arm.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-patches-bot@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=menglong8.dong@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=xukuohai@huaweicloud.com \
    --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