All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	iii@linux.ibm.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix s390 sock_field test failure
Date: Wed, 17 May 2023 04:00:19 +0000	[thread overview]
Message-ID: <168429601993.23839.3806765038041059248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230516214945.1013578-1-yhs@fb.com>

Hello:

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

On Tue, 16 May 2023 14:49:45 -0700 you wrote:
> llvm patch [1] enabled cross-function optimization for func arguments
> (ArgumentPromotion) at -O2 level. And this caused s390 sock_fields
> test failure ([2]). The failure is gone right now as patch [1] was
> reverted in [3]. But it is possible that patch [3] will be reverted
> again and then the test failure in [2] will show up again. So it is
> desirable to fix the failure regardless.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix s390 sock_field test failure
    https://git.kernel.org/bpf/bpf-next/c/de58ef414d8d

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



      reply	other threads:[~2023-05-17  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 21:49 [PATCH bpf-next] selftests/bpf: Fix s390 sock_field test failure Yonghong Song
2023-05-17  4:00 ` 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=168429601993.23839.3806765038041059248.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=iii@linux.ibm.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=yhs@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 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.