From: Randy Dunlap <rdunlap@infradead.org>
To: 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>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Sep 27 (fs/proc/task_mmu.c)
Date: Tue, 26 Sep 2023 22:33:18 -0700 [thread overview]
Message-ID: <cf031327-148a-49c7-a3d3-446d268ca356@infradead.org> (raw)
In-Reply-To: <20230927135132.4019bd9e@canb.auug.org.au>
On 9/26/23 20:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230926:
>
> New tree: overlayfs-fixes
>
> The mm tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 7695
> 5746 files changed, 515623 insertions(+), 144460 deletions(-)
>
> ----------------------------------------------------------------------------
on arm64:
when CONFIG_HUGETLB_PAGE is not set:
../fs/proc/task_mmu.c: In function 'pagemap_scan_thp_entry':
../fs/proc/task_mmu.c:2105:17: error: implicit declaration of function 'pagemap_scan_backout_range'; did you mean 'pagemap_scan_push_range'? [-Werror=implicit-function-declaration]
2105 | pagemap_scan_backout_range(p, start, end);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| pagemap_scan_push_range
cc1: some warnings being treated as errors
aarch64-linux-ar: fs/proc/task_mmu.o: No such file or directory
--
~Randy
parent reply other threads:[~2023-09-27 5:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230927135132.4019bd9e@canb.auug.org.au>]
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=cf031327-148a-49c7-a3d3-446d268ca356@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=usama.anjum@collabora.com \
--cc=viro@zeniv.linux.org.uk \
/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).