All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Khmelevskii <max@linux.ibm.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	bpf@vger.kernel.org, iii@linux.ibm.com, hca@linux.ibm.com,
	gor@linux.ibm.com, agordeev@linux.ibm.com
Subject: Re: [PATCH bpf-next 0/2] s390/bpf: Replace ly instruction with llgf
Date: Tue, 07 Jul 2026 07:40:06 +0000	[thread overview]
Message-ID: <178341000689.1401757.18314278498253295999.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260703125648.919196-4-max@linux.ibm.com>

Hello:

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

On Fri,  3 Jul 2026 14:51:34 +0200 you wrote:
> Sashiko found a bug [1] in 9012cf2491e3, where upper bits of a 64-bit
> register are not zero-extended after ly instruction in used.
> 
> Tested:
>   ./test_progs -v -t get_smp_processor_id
> 
> [1] https://sashiko.dev/#/patchset/20260414142930.528751-1-max%40linux.ibm.com
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] s390/bpf: Replace ly instruction with llgf
    https://git.kernel.org/bpf/bpf-next/c/4abb1bdb600b
  - [bpf-next,2/2] selftests/bpf: Add test for bpf_get_smp_processor_id
    https://git.kernel.org/bpf/bpf-next/c/f71f6c98d1fe

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-07-07  7:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 12:51 [PATCH bpf-next 0/2] s390/bpf: Replace ly instruction with llgf Maxim Khmelevskii
2026-07-03 12:51 ` [PATCH bpf-next 1/2] " Maxim Khmelevskii
2026-07-03 12:51 ` [PATCH bpf-next 2/2] selftests/bpf: Add test for bpf_get_smp_processor_id Maxim Khmelevskii
2026-07-07  7: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=178341000689.1401757.18314278498253295999.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=max@linux.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.