From: patchwork-bot+linux-riscv@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: linux-riscv@lists.infradead.org, ast@kernel.org,
bjorn@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, pulehui@huawei.com, puranjay@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
jiang.biao@linux.dev
Subject: Re: [PATCH bpf-next v4 0/3] bpf: fsession support for riscv
Date: Tue, 24 Mar 2026 06:07:27 +0000 [thread overview]
Message-ID: <177433244748.469836.11256130083444261497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260208053311.698352-1-dongml2@chinatelecom.cn>
Hello:
This series was applied to riscv/linux.git (for-next)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 8 Feb 2026 13:33:08 +0800 you wrote:
> Implement bpf fsession for the riscv architecture.
>
> Changes v4 -> v3:
> * fix the build error
> * v3: https://lore.kernel.org/bpf/20260206122002.1494125-1-dongml2@chinatelecom.cn/
>
> Changes v3 -> v2:
> * fix some comments.
> * v2: https://lore.kernel.org/bpf/20260206115823.1070354-1-dongml2@chinatelecom.cn/T/#t
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] bpf, riscv: introduce emit_store_stack_imm64() for trampoline
https://git.kernel.org/riscv/c/93fd420d71be
- [bpf-next,v4,2/3] bpf, riscv: add fsession support for trampolines
https://git.kernel.org/riscv/c/35b3515be0ec
- [bpf-next,v4,3/3] selftests/bpf: enable fsession_test on riscv64
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-03-24 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 5:33 [PATCH bpf-next v4 0/3] bpf: fsession support for riscv Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 1/3] bpf, riscv: introduce emit_store_stack_imm64() for trampoline Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 2/3] bpf, riscv: add fsession support for trampolines Menglong Dong
2026-02-08 5:33 ` [PATCH bpf-next v4 3/3] selftests/bpf: enable fsession_test on riscv64 Menglong Dong
2026-02-09 13:18 ` [PATCH bpf-next v4 0/3] bpf: fsession support for riscv Pu Lehui
2026-02-11 21:30 ` patchwork-bot+netdevbpf
2026-03-24 6:07 ` patchwork-bot+linux-riscv [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=177433244748.469836.11256130083444261497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jiang.biao@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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