From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
richard -rw- weinberger <richard.weinberger@gmail.com>,
Shile Zhang <shile.zhang@linux.alibaba.com>
Subject: Re: mmotm 2019-11-14-17-24 uploaded (UML mm/vmalloc.c)
Date: Thu, 14 Nov 2019 18:28:06 -0800 [thread overview]
Message-ID: <25f8266e-bba5-d3a3-00e9-d1855e5483c6@infradead.org> (raw)
In-Reply-To: <20191115012505.5C2YGloIj%akpm@linux-foundation.org>
On 11/14/19 5:25 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-11-14-17-24 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
UML on i386 has build errors (defconfig):
CC mm/vmalloc.o
../mm/vmalloc.c: In function ‘__purge_vmap_area_lazy’:
../mm/vmalloc.c:1286:8: error: ‘SHARED_KERNEL_PMD’ undeclared (first use in this function); did you mean ‘PAGE_KERNEL_RO’?
if (!SHARED_KERNEL_PMD && boot_cpu_has(X86_FEATURE_PTI))
^~~~~~~~~~~~~~~~~
PAGE_KERNEL_RO
../mm/vmalloc.c:1286:8: note: each undeclared identifier is reported only once for each function it appears in
../mm/vmalloc.c:1286:29: error: implicit declaration of function ‘boot_cpu_has’; did you mean ‘get_cpu_mask’? [-Werror=implicit-function-declaration]
if (!SHARED_KERNEL_PMD && boot_cpu_has(X86_FEATURE_PTI))
^~~~~~~~~~~~
get_cpu_mask
--
~Randy
prev parent reply other threads:[~2019-11-15 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 1:25 mmotm 2019-11-14-17-24 uploaded akpm
2019-11-15 2:28 ` Randy Dunlap [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=25f8266e-bba5-d3a3-00e9-d1855e5483c6@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=shile.zhang@linux.alibaba.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