mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bjorn@kernel.org, bpf@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, ihor.solodrai@linux.dev,
	puranjay@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
	alex@ghiti.fr, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v3 0/4] riscv, bpf: Prepare for upcoming daily CI
Date: Sun, 11 Oct 2026 13:40:10 +0000	[thread overview]
Message-ID: <179172601001.2055679.10398551714592277673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930083522.1914145-1-pulehui@huaweicloud.com>

Hello:

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

On Wed, 30 Sep 2026 08:35:18 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
> 
> For some time, bpf selftests on riscv64 have suffered from several
> silent breakages and test failures. These mainly stemmed from changes
> such as riscv ftrace atomic patching [0], qemu pmu behavior changes, and
> environment mismatches. While some issues have already been addressed in
> previous patches [1-3] and some are in progress [4], the remaining ones
> are handled in this series.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/4] bpf, riscv: Fix stack-passed arguments for indirect trampolines
    https://git.kernel.org/bpf/bpf-next/c/b4a1ecae94ae
  - [bpf-next,v3,2/4] selftests/bpf: Avoid jiffies quantization error in setget_sockopt
    https://git.kernel.org/bpf/bpf-next/c/153a855d0b3d
  - [bpf-next,v3,3/4] selftests/bpf: Update qemu config for riscv64 in vmtest.sh
    https://git.kernel.org/bpf/bpf-next/c/78142aa07ef6
  - [bpf-next,v3,4/4] selftests/bpf: Update DENYLIST.riscv64
    https://git.kernel.org/bpf/bpf-next/c/52e98bc77f32

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-10-11 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  8:35 Pu Lehui
2026-09-30  8:35 ` [PATCH bpf-next v3 1/4] bpf, riscv: Fix stack-passed arguments for indirect trampolines Pu Lehui
2026-09-30  8:35 ` [PATCH bpf-next v3 2/4] selftests/bpf: Avoid jiffies quantization error in setget_sockopt Pu Lehui
2026-09-30  8:35 ` [PATCH bpf-next v3 3/4] selftests/bpf: Update qemu config for riscv64 in vmtest.sh Pu Lehui
2026-09-30  8:35 ` [PATCH bpf-next v3 4/4] selftests/bpf: Update DENYLIST.riscv64 Pu Lehui
2026-10-11 13:40 ` 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=179172601001.2055679.10398551714592277673.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.com \
    --cc=puranjay@kernel.org \
    --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

all inboxes | Powered by JetHome®