All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andriin@fb.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org, kafai@fb.com,
	songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
	kpsingh@chromium.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix selftest compilation on clang 11
Date: Thu, 10 Dec 2020 16:00:07 +0000	[thread overview]
Message-ID: <160761600775.26295.7600785069556551635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201209142912.99145-1-jolsa@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Wed,  9 Dec 2020 15:29:12 +0100 you wrote:
> We can't compile test_core_reloc_module.c selftest with clang 11,
> compile fails with:
> 
>   CLNG-LLC [test_maps] test_core_reloc_module.o
>   progs/test_core_reloc_module.c:57:21: error: use of unknown builtin \
>   '__builtin_preserve_type_info' [-Wimplicit-function-declaration]
>    out->read_ctx_sz = bpf_core_type_size(struct bpf_testmod_test_read_ctx);
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix selftest compilation on clang 11
    https://git.kernel.org/bpf/bpf-next/c/41003dd0241c

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



      parent reply	other threads:[~2020-12-10 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 14:29 [PATCH bpf-next] selftests/bpf: Fix selftest compilation on clang 11 Jiri Olsa
2020-12-09 20:24 ` Andrii Nakryiko
2020-12-10 16:15   ` Jiri Olsa
     [not found]     ` <CANA3-0dvt3FH8=ZYO7CfW0YKeQemNcsP76j441wW31-WE1_o4A@mail.gmail.com>
2020-12-10 16:36       ` Daniel Borkmann
2020-12-10 16: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=160761600775.26295.7600785069556551635.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@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 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.