Hi all,
On Fri, 12 Mar 2021 12:00:14 +1100 Stephen Rothwell
wrote:
>
> [Cc'ing a few (maybe) interested parties]
>
> On Thu, 11 Mar 2021 07:47:03 +0100 Björn Töpel wrote:
> >
> > On 2021-03-11 01:47, Stephen Rothwell wrote:
> > >
> > > After merging the bpf-next tree, today's linux-next bui
Hi Björn,
[Cc'ing a few (maybe) interested parties]
On Thu, 11 Mar 2021 07:47:03 +0100 Björn Töpel wrote:
>
> On 2021-03-11 01:47, Stephen Rothwell wrote:
> >
> > After merging the bpf-next tree, today's linux-next build (perf) failed
> > like this:
> >
> > make[3]: *** No rule to make target
On 2021-03-11 01:47, Stephen Rothwell wrote:
Hi all,
After merging the bpf-next tree, today's linux-next build (perf) failed
like this:
make[3]: *** No rule to make target 'libbpf_util.h', needed by
'/home/sfr/next/perf/staticobjs/xsk.o'. Stop.
Hi Stephen,
It's an incremental build issue,
Hi all,
After merging the bpf-next tree, today's linux-next build (perf) failed
like this:
make[3]: *** No rule to make target 'libbpf_util.h', needed by
'/home/sfr/next/perf/staticobjs/xsk.o'. Stop.
Caused by commit
7e8bbe24cb8b ("libbpf: xsk: Move barriers from libbpf_util.h to xsk.h")
I
On 12/1/20 9:07 AM, Stephen Rothwell wrote:
Hi all,
After merging the bpf-next tree, today's linux-next build (x86_64
allnoconfig) failed like this:
In file included from fs/select.c:32:
include/net/busy_poll.h: In function 'sk_mark_napi_id_once':
include/net/busy_poll.h:150:36: error: 'const s
Hi all,
After merging the bpf-next tree, today's linux-next build (x86_64
allnoconfig) failed like this:
In file included from fs/select.c:32:
include/net/busy_poll.h: In function 'sk_mark_napi_id_once':
include/net/busy_poll.h:150:36: error: 'const struct sk_buff' has no member
named 'napi_id'
On 9/7/20 8:08 PM, Stephen Rothwell wrote:
Hi all,
After merging the bpf-next tree, today's linux-next build (powerpcle perf)
failed like this:
util/bpf-loader.c: In function 'config_bpf_program':
util/bpf-loader.c:331:2: error: 'bpf_program__title' is deprecated: BPF program
title is confusin
Hi all,
After merging the bpf-next tree, today's linux-next build (powerpcle perf)
failed like this:
util/bpf-loader.c: In function 'config_bpf_program':
util/bpf-loader.c:331:2: error: 'bpf_program__title' is deprecated: BPF program
title is confusing term; please use bpf_program__section_name(
Hi Alexei,
On Tue, 25 Aug 2020 15:34:52 -0700 Alexei Starovoitov
wrote:
>
> On Tue, Aug 25, 2020 at 2:10 PM Stephen Rothwell
> wrote:
> >
> > Hi Alexei,
> >
> > On Tue, 25 Aug 2020 07:33:51 -0700 Alexei Starovoitov
> > wrote:
> > >
> > > what do you suggest to use to make it 'manually enab
On Tue, Aug 25, 2020 at 2:10 PM Stephen Rothwell wrote:
>
> Hi Alexei,
>
> On Tue, 25 Aug 2020 07:33:51 -0700 Alexei Starovoitov
> wrote:
> >
> > what do you suggest to use to make it 'manually enabled' ?
> > All I could think of is to add:
> > depends on !COMPILE_TEST
> > so that allmodconfig d
Hi Alexei,
On Tue, 25 Aug 2020 07:33:51 -0700 Alexei Starovoitov
wrote:
>
> what do you suggest to use to make it 'manually enabled' ?
> All I could think of is to add:
> depends on !COMPILE_TEST
> so that allmodconfig doesn't pick it up.
That is probably sufficient. Some gcc plugins and kasan
On Mon, Aug 24, 2020 at 11:50 PM Stephen Rothwell wrote:
>
> Hi Alexei,
>
> On Mon, 24 Aug 2020 20:27:28 -0700 Alexei Starovoitov
> wrote:
> >
> > I didn't receive the first email you've replied to.
> > The build error is:
> > "
> > No libelf found
> > make[5]: *** [Makefile:284: elfdep] Error 1
Hi Alexei,
On Mon, 24 Aug 2020 20:27:28 -0700 Alexei Starovoitov
wrote:
>
> I didn't receive the first email you've replied to.
> The build error is:
> "
> No libelf found
> make[5]: *** [Makefile:284: elfdep] Error 1
> "
> and build process stops because libelf is not found, right?
> That is ex
On Mon, Aug 24, 2020 at 8:04 PM Stephen Rothwell wrote:
>
> Hi Alexei,
>
> On Mon, 24 Aug 2020 18:25:44 -0700 Alexei Starovoitov
> wrote:
> >
> > On Mon, Aug 24, 2020 at 6:20 PM Stephen Rothwell
> > wrote:
> > >
> > > On Fri, 21 Aug 2020 11:11:11 +1000 Stephen Rothwell
> > > wrote:
> > > >
>
Hi Alexei,
On Mon, 24 Aug 2020 18:25:44 -0700 Alexei Starovoitov
wrote:
>
> On Mon, Aug 24, 2020 at 6:20 PM Stephen Rothwell
> wrote:
> >
> > On Fri, 21 Aug 2020 11:11:11 +1000 Stephen Rothwell
> > wrote:
> > >
> > > After merging the bpf-next tree, today's linux-next build (x86_64
> > > a
On Mon, Aug 24, 2020 at 6:20 PM Stephen Rothwell wrote:
>
> Hi all,
>
> On Fri, 21 Aug 2020 11:11:11 +1000 Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the bpf-next tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > Auto-detecting system feature
Hi all,
On Fri, 21 Aug 2020 11:11:11 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> Auto-detecting system features:
> ...libelf: [ [31mOFF[m ]
> ...
Hi all,
After merging the bpf-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
Auto-detecting system features:
...libelf: [ [31mOFF[m ]
... zlib: [ [31mOFF[m ]
... bpf: [ [32mon[m ]
No li
Hi Jiri,
On Tue, Jul 14, 2020 at 10:33 AM Jiri Olsa wrote:
> On Tue, Jul 14, 2020 at 08:16:54AM +0200, Jiri Olsa wrote:
> > On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote:
> > > After merging the bpf-next tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like
On Tue, Jul 14, 2020 at 08:16:54AM +0200, Jiri Olsa wrote:
> On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the bpf-next tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > tmp/ccsqpVCY.s: Assembler messages:
>
On Tue, Jul 14, 2020 at 12:22:47PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> tmp/ccsqpVCY.s: Assembler messages:
> tmp/ccsqpVCY.s:78: Error: unrecognized symbol type ""
> tmp/ccsqpVCY.s:9
Hi all,
After merging the bpf-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
tmp/ccsqpVCY.s: Assembler messages:
tmp/ccsqpVCY.s:78: Error: unrecognized symbol type ""
tmp/ccsqpVCY.s:91: Error: unrecognized symbol type ""
I don't know what has caused this (I guess
Hi all,
On Mon, 1 Jul 2019 14:57:22 +1000 Stephen Rothwell
wrote:
>
> After merging the bpf-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_main.c:1605:5: error: conflicting
> types for 'mlx5e_open_cq'
> int mlx5e_o
Hi all,
After merging the bpf-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/net/ethernet/mellanox/mlx5/core/en_main.c:1605:5: error: conflicting
types for 'mlx5e_open_cq'
int mlx5e_open_cq(struct mlx5e_channel *c, struct dim_cq_moder moder,
^~~
On Wed, Feb 27, 2019 at 5:31 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> kernel/sysctl.c:1238:13: error: 'sysctl_bpf_stats_enabled' undeclared here
> (not in a function); did you mean 'sysctl
Hi all,
After merging the bpf-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
kernel/sysctl.c:1238:13: error: 'sysctl_bpf_stats_enabled' undeclared here (not
in a function); did you mean 'sysctl_base_table'?
.data = &sysctl_bpf_stats_enabled,
^
On Wed, Dec 13, 2017 at 12:32:45PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> kernel/events/core.o: In function `perf_ioctl':
> core.c:(.text+0x98c4): undefined reference to `bpf_event_que
Hi all,
After merging the bpf-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
kernel/events/core.o: In function `perf_ioctl':
core.c:(.text+0x98c4): undefined reference to `bpf_event_query_prog_array'
Caused by commit
f371b304f12e ("bpf/tracing: allow user space
28 matches
Mail list logo
