From: Florent Revest <revest@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Florent Revest <revest@google.com>, bpf <bpf@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 7 (bpf: sock_from_file)
Date: Mon, 07 Dec 2020 20:44:01 +0100 [thread overview]
Message-ID: <bc37337ff82e187e39d029ee9f488d81e2b4fb44.camel@chromium.org> (raw)
In-Reply-To: <b8f2e76b-a35e-55c5-e937-eea81700c994@infradead.org>
On Mon, 2020-12-07 at 10:39 -0800, Randy Dunlap wrote:
> On 12/7/20 1:25 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20201204:
> >
>
> on i386:
> # CONFIG_NET is not set
>
> ld: kernel/trace/bpf_trace.o: in function `bpf_sock_from_file':
> bpf_trace.c:(.text+0xe23): undefined reference to `sock_from_file'
>
Thanks Randy! I'm on it, I'll send a fix to bpf-next.
prev parent reply other threads:[~2020-12-07 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 9:25 linux-next: Tree for Dec 7 Stephen Rothwell
2020-12-07 18:39 ` linux-next: Tree for Dec 7 (bpf: sock_from_file) Randy Dunlap
2020-12-07 19:44 ` Florent Revest [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=bc37337ff82e187e39d029ee9f488d81e2b4fb44.camel@chromium.org \
--to=revest@chromium.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=revest@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).