linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stanislav Fomichev <sdf@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bpf <bpf@vger.kernel.org>
Subject: Re: linux-next: Tree for Apr 24 (kernel/bpf/cgroup.c)
Date: Fri, 24 Apr 2020 11:07:40 -0700	[thread overview]
Message-ID: <CAEf4BzaEjNKU0rV-im2aU1j0xrdYZhC61OLnu31iWy8G4S+yew@mail.gmail.com> (raw)
In-Reply-To: <f11ce3ab-9ede-6241-d648-1a2b34e1ea4b@infradead.org>

On Fri, Apr 24, 2020 at 8:30 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 4/24/20 12:48 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200423:
> >
>
> on i386:
>
> ld: kernel/bpf/cgroup.o: in function `cgroup_base_func_proto.isra.11':
> cgroup.c:(.text+0x14a1): undefined reference to `bpf_event_output_data_proto'
> ld: cgroup.c:(.text+0x14c1): undefined reference to `bpf_base_func_proto'
>

Stanislav, could you please take a look?

> Full randconfig file is attached.
>
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>

  reply	other threads:[~2020-04-24 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  7:48 linux-next: Tree for Apr 24 Stephen Rothwell
2020-04-24 15:28 ` linux-next: Tree for Apr 24 (kernel/bpf/cgroup.c) Randy Dunlap
2020-04-24 18:07   ` Andrii Nakryiko [this message]
2020-04-24 18:12     ` Stanislav Fomichev
2020-04-24 15:42 ` linux-next: Tree for Apr 24 (net/openvswitch/) Randy Dunlap

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=CAEf4BzaEjNKU0rV-im2aU1j0xrdYZhC61OLnu31iWy8G4S+yew@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sdf@google.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).