mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: chenhuacai@kernel.org, hengqi.chen@gmail.com, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
	memxor@gmail.com, loongarch@lists.linux.dev, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Enable timed may_goto tests for LoongArch
Date: Mon, 17 Aug 2026 09:20:08 +0000	[thread overview]
Message-ID: <178695840866.1036045.17681524436560512940.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813070906.5164-1-yangtiezhu@loongson.cn>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 13 Aug 2026 15:09:06 +0800 you wrote:
> Enable stream_cond_break, may_goto_interaction, and verifier_may_goto_1
> tests for LoongArch, aligning with recent architectural infrastructure
> support (timed may_goto and arch_bpf_stack_walk JIT).
> 
> With this patch, the following tests passed on LoongArch:
> 
>   sudo ./test_progs -a stream_success/stream_cond_break
>   sudo ./test_progs -a verifier_bpf_fastcall/may_goto_interaction
>   sudo ./test_progs -a verifier_may_goto_1
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1] selftests/bpf: Enable timed may_goto tests for LoongArch
    https://git.kernel.org/bpf/bpf-next/c/77877bf570ff

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-08-17  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13  7:09 Tiezhu Yang
2026-08-13  8:11 ` bot+bpf-ci
2026-08-13  8:24   ` Tiezhu Yang
2026-08-17  9:20 ` 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=178695840866.1036045.17681524436560512940.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=chenhuacai@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=hengqi.chen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=memxor@gmail.com \
    --cc=yangtiezhu@loongson.cn \
    /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®