From: Stephen Rothwell <sfr@canb.auug.org.au> To: Daniel Borkmann <daniel@iogearbox.net>, Alexei Starovoitov <ast@kernel.org>, Networking <netdev@vger.kernel.org> Cc: Linux Next Mailing List <linux-next@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, ppc-dev <linuxppc-dev@lists.ozlabs.org> Subject: linux-next: build warning after merge of the bpf-next tree Date: Fri, 18 Oct 2019 10:56:57 +1100 [thread overview] Message-ID: <20191018105657.4584ec67@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 389 bytes --] Hi all, After merging the bpf-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: WARNING: 2 bad relocations c000000001998a48 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_start c000000001998a50 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_end Introduced by commit 8580ac9404f6 ("bpf: Process in-kernel BTF") -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au> To: Daniel Borkmann <daniel@iogearbox.net>, Alexei Starovoitov <ast@kernel.org>, Networking <netdev@vger.kernel.org> Cc: Linux Next Mailing List <linux-next@vger.kernel.org>, ppc-dev <linuxppc-dev@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: linux-next: build warning after merge of the bpf-next tree Date: Fri, 18 Oct 2019 10:56:57 +1100 [thread overview] Message-ID: <20191018105657.4584ec67@canb.auug.org.au> (raw) [-- Attachment #1: Type: text/plain, Size: 389 bytes --] Hi all, After merging the bpf-next tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: WARNING: 2 bad relocations c000000001998a48 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_start c000000001998a50 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_end Introduced by commit 8580ac9404f6 ("bpf: Process in-kernel BTF") -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-10-17 23:57 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-17 23:56 Stephen Rothwell [this message] 2019-10-17 23:56 ` linux-next: build warning after merge of the bpf-next tree Stephen Rothwell 2019-10-18 5:01 ` Alexei Starovoitov 2019-10-18 5:01 ` Alexei Starovoitov 2019-10-28 0:02 ` Stephen Rothwell 2019-10-28 0:02 ` Stephen Rothwell 2020-01-10 22:28 ` Alexandre Ghiti 2020-01-10 22:28 ` Alexandre Ghiti 2020-01-10 22:28 ` Alexandre Ghiti 2020-01-10 23:18 ` Alexei Starovoitov 2020-01-10 23:18 ` Alexei Starovoitov 2020-01-10 23:18 ` Alexei Starovoitov 2020-01-11 14:06 ` Alexandre Ghiti 2020-01-11 14:06 ` Alexandre Ghiti 2020-01-11 14:06 ` Alexandre Ghiti 2020-01-11 0:20 ` Palmer Dabbelt 2020-01-11 0:20 ` Palmer Dabbelt 2020-01-11 0:20 ` Palmer Dabbelt 2020-01-11 14:31 ` Alexandre Ghiti 2020-01-11 14:31 ` Alexandre Ghiti 2020-01-11 14:31 ` Alexandre Ghiti 2020-01-13 4:33 ` Zong Li 2020-01-13 4:33 ` Zong Li 2020-01-13 4:33 ` Zong Li 2020-01-14 5:23 ` Alexei Starovoitov 2020-01-14 5:23 ` Alexei Starovoitov 2020-01-14 5:23 ` Alexei Starovoitov 2020-01-15 20:48 ` Alexandre Ghiti 2020-01-15 20:48 ` Alexandre Ghiti 2020-01-15 20:48 ` Alexandre Ghiti -- strict thread matches above, loose matches on Subject: below -- 2024-02-06 4:33 Stephen Rothwell 2023-10-13 0:40 Stephen Rothwell 2023-10-13 5:30 ` Stephen Rothwell 2023-10-13 16:54 ` Martin KaFai Lau 2023-02-15 3:45 Stephen Rothwell 2023-02-06 3:54 Stephen Rothwell 2023-02-06 3:59 ` Alexei Starovoitov 2021-12-05 23:55 Stephen Rothwell 2021-12-06 0:43 ` Stephen Rothwell 2021-12-07 3:22 ` Andrii Nakryiko 2020-11-11 1:01 Stephen Rothwell 2020-11-11 14:03 ` Qian Cai 2020-11-11 18:15 ` Andrii Nakryiko 2020-07-14 2:16 Stephen Rothwell 2020-07-14 9:00 ` Jiri Olsa 2020-07-14 9:27 ` Geert Uytterhoeven 2020-07-14 10:33 ` Stephen Rothwell 2020-07-14 10:47 ` Jiri Olsa 2020-07-14 11:15 ` Jiri Olsa 2020-07-14 14:54 ` Alexei Starovoitov 2019-03-24 22:28 Stephen Rothwell 2019-03-24 22:39 ` Willem de Bruijn 2018-05-09 4:49 Stephen Rothwell
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=20191018105657.4584ec67@canb.auug.org.au \ --to=sfr@canb.auug.org.au \ --cc=ast@kernel.org \ --cc=daniel@iogearbox.net \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-next@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=netdev@vger.kernel.org \ /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: linkBe 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.