From: patchwork-bot+netdevbpf@kernel.org
To: Sasha Levin <sashal@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
vgupta@kernel.org, bcain@kernel.org, shorne@gmail.com,
josef@toxicpanda.com, eddyz87@gmail.com, memxor@gmail.com,
jonas@southpole.se, stefan.kristiansson@saunalahti.fi,
peterz@infradead.org, will@kernel.org, boqun@kernel.org,
mark.rutland@arm.com, mhiramat@kernel.org, bpf@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
linux-hexagon@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-kernel@vger.kernel.org, bot@kernelci.org, lkp@intel.com
Subject: Re: [PATCH bpf-next] locking/atomic: arc, hexagon, openrisc: Define arch_cmpxchg_local()
Date: Sun, 18 Oct 2026 15:30:07 +0000 [thread overview]
Message-ID: <179233740728.1716327.4924636966415964247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261018132907.3823160-1-sashal@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 18 Oct 2026 09:29:07 -0400 you wrote:
> Commit ccb88db8dac8 ("bpf: Don't hand out a linked element as extra
> element") made alloc_htab_elem() take the per-cpu spare element with
> try_cmpxchg_local(), the first caller of cmpxchg_local() outside of
> architecture code. It doesn't build on arc, hexagon and openrisc:
>
> include/linux/atomic/atomic-arch-fallback.h:384:27: error: implicit declaration of function 'arch_cmpxchg_local'; did you mean 'raw_cmpxchg_local'? [-Werror=implicit-function-declaration]
>
> [...]
Here is the summary with links:
- [bpf-next] locking/atomic: arc, hexagon, openrisc: Define arch_cmpxchg_local()
https://git.kernel.org/bpf/bpf-next/c/8cebaa3be829
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-18 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 13:29 Sasha Levin
2026-10-18 15:27 ` Alexei Starovoitov
2026-10-18 15:30 ` 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=179233740728.1716327.4924636966415964247.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bcain@kernel.org \
--cc=boqun@kernel.org \
--cc=bot@kernelci.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jonas@southpole.se \
--cc=josef@toxicpanda.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=memxor@gmail.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=vgupta@kernel.org \
--cc=will@kernel.org \
/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®