BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com
Subject: Re: [PATCH bpf] selftests/bpf: Add lru_bug to s390x deny list
Date: Fri, 12 Aug 2022 16:50:14 +0000	[thread overview]
Message-ID: <166032301462.8174.3605479061639065308.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220810200710.1300299-1-deso@posteo.net>

Hello:

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

On Wed, 10 Aug 2022 20:07:10 +0000 you wrote:
> The lru_bug BPF selftest is failing execution on s390x machines. The
> failure is due to program attachment failing in turn, similar to a bunch
> of other tests. Those other tests have already been deny-listed and with
> this change we do the same for the lru_bug test, adding it to the
> corresponding file.
> 
> Fixes: de7b9927105b ("selftests/bpf: Add test for prealloc_lru_pop bug")
> Signed-off-by: Daniel Müller <deso@posteo.net>
> 
> [...]

Here is the summary with links:
  - [bpf] selftests/bpf: Add lru_bug to s390x deny list
    https://git.kernel.org/bpf/bpf/c/27e23836ce22

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



      parent reply	other threads:[~2022-08-12 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 20:07 [PATCH bpf] selftests/bpf: Add lru_bug to s390x deny list Daniel Müller
2022-08-11  0:27 ` Mykola Lysenko
2022-08-12 16:50 ` 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=166032301462.8174.3605479061639065308.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Daniel_M=C3=BCller_=3Cdeso=40posteo=2Enet=3E?=@ci.codeaurora.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox