public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Menglong Dong <menglong.dong@linux.dev>
To: "Menglong Dong" <menglong8.dong@gmail.com>,
	"Björn Töpel" <bjorn@kernel.org>
Cc: 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, pulehui@huawei.com, puranjay@kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, jiang.biao@linux.dev, bpf@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Leon Hwang <leon.hwang@linux.dev>
Subject: Re: [PATCH bpf-next 0/3] bpf: fsession support for riscv
Date: Fri, 06 Feb 2026 19:29:30 +0800	[thread overview]
Message-ID: <2830483.mvXUDI8C0e@7950hx> (raw)
In-Reply-To: <CAJ+HfNh63kg7QNOVhn4As1nGBLDLEy72zaiz0i2+CZKe=f9WuA@mail.gmail.com>

On 2026/2/6 19:20, Björn Töpel wrote:
> Thank you for working on this!
> 
> On Tue, 3 Feb 2026 at 06:52, Menglong Dong <menglong8.dong@gmail.com> wrote:
> >
> > Implement bpf fsession for the riscv architecture.
> >
> > Menglong Dong (3):
> >   bpf,riscv: introduce emit_store_stack_imm64() for trampoline
> >   bpf,riscv: add fsession support for trampolines
> >   selftests/bpf: enable fsession_test on riscv64
> 
> I'm happy with either addressing Leon's comment with a follow-up, or
> spinning a V2.
> 
> For this version plus Leon's nit as a follow-up, or a V2:
> Tested-by: Björn Töpel <bjorn@kernel.org> # QEMU/RVA23/DT
> Acked-by: Björn Töpel <bjorn@kernel.org>

Hi, Björn. Thanks for your reviewing and testing. I'll send a V2
now :)

> 
> 





      reply	other threads:[~2026-02-06 11:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03  5:52 [PATCH bpf-next 0/3] bpf: fsession support for riscv Menglong Dong
2026-02-03  5:52 ` [PATCH bpf-next 1/3] bpf, riscv: introduce emit_store_stack_imm64() for trampoline Menglong Dong
2026-02-03  5:52 ` [PATCH bpf-next 2/3] bpf, riscv: add fsession support for trampolines Menglong Dong
2026-02-03  6:20   ` Leon Hwang
2026-02-03  6:25     ` Menglong Dong
2026-02-06 11:22   ` Björn Töpel
2026-02-06 12:07     ` Menglong Dong
2026-02-03  5:52 ` [PATCH bpf-next 3/3] selftests/bpf: enable fsession_test on riscv64 Menglong Dong
2026-02-06 11:20 ` [PATCH bpf-next 0/3] bpf: fsession support for riscv Björn Töpel
2026-02-06 11:29   ` Menglong Dong [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=2830483.mvXUDI8C0e@7950hx \
    --to=menglong.dong@linux.dev \
    --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=leon.hwang@linux.dev \
    --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