From: John Hubbard <jhubbard@nvidia.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Song Liu <songliubraving@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
<bpf@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/1] bpf: fix a no-mmu build failure by providing a stub allocator
Date: Mon, 25 Nov 2019 15:41:02 -0800 [thread overview]
Message-ID: <20191125234103.1699950-1-jhubbard@nvidia.com> (raw)
Hi,
I ran into this on today's linux-next: commit c165016bac27 ("Add
linux-next specific files for 20191125"). The kbuild robot reported a
build failure on my larger (unrelated) patchset, but there were actually
two build failures, and this patch here fixes the second failure.
John Hubbard (1):
bpf: fix a no-mmu build failure by providing a stub allocator
kernel/bpf/syscall.c | 7 +++++++
1 file changed, 7 insertions(+)
--
2.24.0
next reply other threads:[~2019-11-25 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 23:41 John Hubbard [this message]
2019-11-25 23:41 ` [PATCH] bpf: fix a no-mmu build failure by providing a stub allocator John Hubbard
2019-11-25 23:43 ` Daniel Borkmann
2019-11-25 23:45 ` John Hubbard
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=20191125234103.1699950-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=andriin@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hannes@cmpxchg.org \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
/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).