[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191125234103.1699950-1-jhubbard@nvidia.com>
Date: Mon, 25 Nov 2019 15:41:02 -0800
From: John Hubbard <jhubbard@...dia.com>
To: Andrii Nakryiko <andriin@...com>
CC: Daniel Borkmann <daniel@...earbox.net>,
Song Liu <songliubraving@...com>,
John Fastabend <john.fastabend@...il.com>,
Johannes Weiner <hannes@...xchg.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
<bpf@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
John Hubbard <jhubbard@...dia.com>
Subject: [PATCH 0/1] bpf: fix a no-mmu build failure by providing a stub allocator
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
Powered by blists - more mailing lists