From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com
Subject: Re: [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock
Date: Thu, 24 Apr 2025 18:33:30 +0000 [thread overview]
Message-ID: <174551961000.3446286.10420854203925676664.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250424165525.154403-1-iii@linux.ibm.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Apr 2025 18:41:24 +0200 you wrote:
> Hi,
>
> I tried running the arena_spin_lock test on s390x and ran into the
> following issues:
>
> * Changing the header file does not lead to rebuilding the test.
> * The checked for number of CPUs and the actually required number of
> CPUs are different.
> * Endianness issue in spinlock definition.
>
> [...]
Here is the summary with links:
- [1/3] selftests/bpf: Fix arena_spin_lock.c build dependency
https://git.kernel.org/netdev/net-next/c/4fe09ff1a54a
- [2/3] selftests/bpf: Fix arena_spin_lock on systems with less than 16 CPUs
(no matching commit)
- [3/3] selftests/bpf: Fix endianness issue in __qspinlock declaration
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-04-24 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:41 [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock Ilya Leoshkevich
2025-04-24 16:41 ` [PATCH 1/3] selftests/bpf: Fix arena_spin_lock.c build dependency Ilya Leoshkevich
2025-04-24 16:41 ` [PATCH 2/3] selftests/bpf: Fix arena_spin_lock on systems with less than 16 CPUs Ilya Leoshkevich
2025-04-24 16:41 ` [PATCH 3/3] selftests/bpf: Fix endianness issue in __qspinlock declaration Ilya Leoshkevich
2025-04-24 18:33 ` patchwork-bot+netdevbpf [this message]
2025-04-24 18:41 ` [PATCH 0/3] selftests/bpf: Fix a few issues in arena_spin_lock Alexei Starovoitov
2025-04-24 18:51 ` Konstantin Ryabitsev
2025-04-25 16:25 ` Jakub Kicinski
2025-04-25 17:18 ` Konstantin Ryabitsev
2025-04-25 18:58 ` Konstantin Ryabitsev
2025-04-26 0:32 ` Alexei Starovoitov
2025-04-25 0:10 ` patchwork-bot+netdevbpf
2025-04-25 0:16 ` Alexei Starovoitov
2025-04-25 0:40 ` patchwork-bot+netdevbpf
2025-04-25 1:14 ` Alexei Starovoitov
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=174551961000.3446286.10420854203925676664.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 \
/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.