Hi all,
On Wed, 30 Sep 2020 14:07:15 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/btf.c
>
> between commit:
>
> 1245008122d7 ("libbpf: Fix native endian assumption when parsing BTF")
>
> from the bpf tree and commit:
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/btf.c
between commit:
1245008122d7 ("libbpf: Fix native endian assumption when parsing BTF")
from the bpf tree and commit:
3289959b97ca ("libbpf: Support BTF loading and raw data output in both
endia
Hi all,
On Fri, 26 Jun 2020 10:05:27 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/progs/bpf_iter_netlink.c
>
> between commits:
>
> 9c82a63cf370 ("libbpf: Fix CO-RE relocs against .text section")
> 647
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/testing/selftests/bpf/progs/bpf_iter_netlink.c
between commits:
9c82a63cf370 ("libbpf: Fix CO-RE relocs against .text section")
647b502e3d54 ("selftests/bpf: Refactor some net macros to bpf_tracing_net.h")
fro
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
kernel/bpf/verifier.c
between commit:
e92888c72fbd ("bpf: Enforce returning 0 for fentry/fexit progs")
from the bpf tree and commit:
15d83c4d7cef ("bpf: Allow loading of a bpf_iter program")
from the bpf-next tree
Hi all,
This is now a conflict between the net and net-next trees.
On Wed, 9 Oct 2019 09:47:25 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/Makefile
>
> between commit:
>
> 1bd63524593b ("libbpf: handle symbol versio
Hi all,
This is now a conflict between the net and net-next trees.
On Tue, 8 Oct 2019 09:48:40 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/Makefile
>
> between commit:
>
> 1bd63524593b ("libbpf: handle symbol versio
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/Makefile
between commit:
1bd63524593b ("libbpf: handle symbol versioning properly for libbpf.a")
from the bpf tree and commit:
e01a75c15969 ("libbpf: Move bpf_{helpers, helper_defs, endian, tracing}.h
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/Makefile
between commit:
1bd63524593b ("libbpf: handle symbol versioning properly for libbpf.a")
from the bpf tree and commit:
a9eb048d5615 ("libbpf: Add cscope and tags targets to Makefile")
from th
Hi Jakub,
On Mon, 14 May 2018 13:41:40 -0700 Jakub Kicinski
wrote:
>
> On Mon, 14 May 2018 11:57:00 +1000, Stephen Rothwell wrote:
> > diff --cc tools/lib/bpf/libbpf.c
> > index 8da4eeb101a6,df54c4c9e48a..
> > --- a/tools/lib/bpf/libbpf.c
> > +++ b/tools/lib/bpf/libbpf.c
> > @@@ -216
On Mon, 14 May 2018 11:57:00 +1000, Stephen Rothwell wrote:
> diff --cc tools/lib/bpf/libbpf.c
> index 8da4eeb101a6,df54c4c9e48a..
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@@ -2163,9 -2193,12 +2193,12 @@@ int bpf_prog_load_xattr(const struct bp
>
> if (!
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/libbpf.c
between commit:
3597683c9da6 ("tools: bpf: handle NULL return in bpf_prog_load_xattr()")
from the bpf tree and commit:
17387dd5ac2c ("tools: bpf: don't complain about no kernel version for
n
> On May 1, 2018, at 10:50 PM, Stephen Rothwell wrote:
>
> Hi Song,
>
> On Wed, 2 May 2018 04:40:20 + Song Liu wrote:
>>
>>> - CHECK(build_id_matches < 1, "build id match",
>>> - "Didn't find expected build ID from the map\n");
>>> + if (CHECK(build_id_matches < 1, "build id
Hi Song,
On Wed, 2 May 2018 04:40:20 + Song Liu wrote:
>
> > - CHECK(build_id_matches < 1, "build id match",
> > - "Didn't find expected build ID from the map\n");
> > + if (CHECK(build_id_matches < 1, "build id match",
> > - "Didn't find expected build ID from the map
> On May 1, 2018, at 7:09 PM, Stephen Rothwell wrote:
>
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/test_progs.c
>
> between commit:
>
> a4e21ff8d9a3 ("bpf: minor fix to selftest test_stacktrace_build_id()")
>
> from the
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/testing/selftests/bpf/test_progs.c
between commit:
a4e21ff8d9a3 ("bpf: minor fix to selftest test_stacktrace_build_id()")
from the bpf tree and commit:
79b453501310 ("tools/bpf: add a test for bpf_get_stack w
On 04/26/2018 02:53 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> samples/sockmap/Makefile
>
> between commit:
>
> 4dfe1bb95235 ("bpf: sockmap sample use clang flag, -target bpf")
>
> from the bpf tree and commit:
>
> 2e04
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
samples/sockmap/Makefile
between commit:
4dfe1bb95235 ("bpf: sockmap sample use clang flag, -target bpf")
from the bpf tree and commit:
2e04eb1dd1ca ("bpf: sockmap, remove samples program")
from the bpf-next tree.
Hi Dave,
On Mon, 26 Feb 2018 11:41:47 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/test_verifier.c
>
> between commit:
>
> ca36960211eb ("bpf: allow xadd only on aligned memory")
>
> from the bpf tree a
On 02/26/2018 01:41 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/testing/selftests/bpf/test_verifier.c
>
> between commit:
>
> ca36960211eb ("bpf: allow xadd only on aligned memory")
>
> from the bpf tree and commit:
>
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/testing/selftests/bpf/test_verifier.c
between commit:
ca36960211eb ("bpf: allow xadd only on aligned memory")
from the bpf tree and commit:
23d191a82c13 ("bpf: add various jit test cases")
from the bpf-next
21 matches
Mail list logo
