All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, john.fastabend@gmail.com,
	martin.lau@linux.dev, stfomichev@gmail.com, willemb@google.com
Subject: Re: [PATCH bpf] selftests/bpf: adapt one more case in test_lru_map to the new target_free
Date: Wed, 25 Jun 2025 22:30:07 +0000	[thread overview]
Message-ID: <175089060751.641624.12110903845868703382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250625210412.2732970-1-willemdebruijn.kernel@gmail.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 25 Jun 2025 17:03:55 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> The below commit that updated BPF_MAP_TYPE_LRU_HASH free target,
> also updated tools/testing/selftests/bpf/test_lru_map to match.
> 
> But that missed one case that passes with 4 cores, but fails at
> higher cpu counts.
> 
> [...]

Here is the summary with links:
  - [bpf] selftests/bpf: adapt one more case in test_lru_map to the new target_free
    https://git.kernel.org/bpf/bpf/c/5e9388f7984a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-06-25 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 21:03 [PATCH bpf] selftests/bpf: adapt one more case in test_lru_map to the new target_free Willem de Bruijn
2025-06-25 22: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=175089060751.641624.12110903845868703382.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=stfomichev@gmail.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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.