From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: mmotm 2019-01-30-15-02 uploaded (i386 build summary)
Date: Wed, 30 Jan 2019 19:15:27 -0800 [thread overview]
Message-ID: <c19c92ac-2490-4342-4cc1-276b5bf5ea8f@infradead.org> (raw)
In-Reply-To: <20190130230305.d7osZ%akpm@linux-foundation.org>
On 1/30/19 3:03 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-01-30-15-02 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.
>
argghh. I guess nobody builds on i386 any more.
Summary from 8 i386 builds:
(ignoring "missing braces" in drm)
../kernel/dma/swiotlb.c:211:9: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘size_t’ [-Wformat=]
../kernel/dma/swiotlb.c:217:9: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘size_t’ [-Wformat=]
ld: drivers/mtd/nand/raw/meson_nand.o: in function `meson_nfc_setup_data_interface':
meson_nand.c:(.text+0x1f9): undefined reference to `__udivdi3'
../arch/x86/platform/olpc/olpc_dt.c:146:10: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘size_t’ [-Wformat=]
../mm/memcontrol.c:5629:52: error: ‘THP_FAULT_ALLOC’ undeclared (first use in this function)
../mm/memcontrol.c:5631:17: error: ‘THP_COLLAPSE_ALLOC’ undeclared (first use in this function)
../mm/memcontrol.c:5629:52: error: ‘THP_FAULT_ALLOC’ undeclared (first use in this function)
../mm/memcontrol.c:5631:17: error: ‘THP_COLLAPSE_ALLOC’ undeclared (first use in this function)
--
~Randy
prev parent reply other threads:[~2019-01-31 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 23:03 mmotm 2019-01-30-15-02 uploaded akpm
2019-01-31 3:15 ` 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=c19c92ac-2490-4342-4cc1-276b5bf5ea8f@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=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