All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	emil@etsalapatis.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Rename libarena struct bitmap to struct arena_bitmap
Date: Wed, 08 Jul 2026 03:20:05 +0000	[thread overview]
Message-ID: <178348080592.2269416.13888096250636232840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260707220136.910374-1-yonghong.song@linux.dev>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Tue,  7 Jul 2026 15:01:36 -0700 you wrote:
> When building bpf selftest with latest bpf-next, I got the following failure:
> 
>   In file included from /home/yhs/work/bpf-next/tools/testing/selftests/bpf/libarena/selftests/test_parallel_bitmap.bpf.c:8:
>   /home/yhs/work/bpf-next/tools/testing/selftests/bpf/libarena/include/libarena/bitmap.h:11:8: error: redefinition of
>         'bitmap'
>      11 | struct bitmap {
>         |        ^
>   /home/yhs/work/bpf-next/tools/testing/selftests/bpf/tools/include/vmlinux.h:51320:8: note: previous definition is here
>    51320 | struct bitmap {
>          |        ^
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Rename libarena struct bitmap to struct arena_bitmap
    https://git.kernel.org/bpf/bpf-next/c/ee1bcf8271eb

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 22:01 [PATCH bpf-next] selftests/bpf: Rename libarena struct bitmap to struct arena_bitmap Yonghong Song
2026-07-07 22:14 ` Emil Tsalapatis
2026-07-08  3: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=178348080592.2269416.13888096250636232840.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=daniel@iogearbox.net \
    --cc=emil@etsalapatis.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@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 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.