BPF List
 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, mykolal@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: fix btf_dump/btf_dump due to recent clang change
Date: Mon, 23 May 2022 20:00:12 +0000	[thread overview]
Message-ID: <165333601248.24888.11360657395318959311.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220523152044.3905809-1-yhs@fb.com>

Hello:

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

On Mon, 23 May 2022 08:20:44 -0700 you wrote:
> Latest llvm-project upstream had a change of behavior
> related to qualifiers on function return type ([1]).
> This caused selftests btf_dump/btf_dump failure.
> The following example shows what changed.
> 
>   $ cat t.c
>   typedef const char * const (* const (* const fn_ptr_arr2_t[5])())(char * (*)(int));
>   struct t {
>     int a;
>     fn_ptr_arr2_t l;
>   };
>   int foo(struct t *arg) {
>     return arg->a;
>   }
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: fix btf_dump/btf_dump due to recent clang change
    https://git.kernel.org/bpf/bpf-next/c/4050764cbaa2

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



      reply	other threads:[~2022-05-23 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 15:20 [PATCH bpf-next] selftests/bpf: fix btf_dump/btf_dump due to recent clang change Yonghong Song
2022-05-23 20: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=165333601248.24888.11360657395318959311.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=kernel-team@fb.com \
    --cc=mykolal@fb.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox