public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google•com>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: open list <linux-kernel@vger•kernel.org>,
	Linux-Next Mailing List <linux-next@vger•kernel.org>,
	regressions@lists•linux.dev, lkft-triage@lists•linaro.org,
	Hugh Dickins <hughd@google•com>,
	Alistair Popple <apopple@nvidia•com>,
	David Hildenbrand <david@redhat•com>,
	Greg Thelen <gthelen@google•com>,
	Johannes Weiner <hannes@cmpxchg•org>,
	"Kirill A. Shutemov" <kirill@shutemov•name>,
	Matthew Wilcox <willy@infradead•org>,
	Michal Hocko <mhocko@suse•com>, Rik van Riel <riel@surriel•com>,
	Shakeel Butt <shakeelb@google•com>,
	Suren Baghdasaryan <surenb@google•com>,
	Vlastimil Babka <vbabka@suse•cz>, Yu Zhao <yuzhao@google•com>,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: mm/munlock: mlock_page() munlock_page() batch by pagevec
Date: Wed, 9 Feb 2022 20:49:57 -0800 (PST)	[thread overview]
Message-ID: <5d63a397-96e-7e9a-eb9f-289904f9998@google.com> (raw)
In-Reply-To: <CA+G9fYv_ssRhvYi4mM1ZeGCL2meFwRsakpADp_Cz3bNDZz2zSA@mail.gmail.com>

On Wed, 9 Feb 2022, Naresh Kamboju wrote:
> The following build regression noticed while building Linux next 20220209
> arm/riscv/sh of allnoconfig and tinyconfig builds failed with gcc-10,
> gcc-11 and clang-13.
> 
> clang: warning: argument unused during compilation: '-march=armv7-m'
> [-Wunused-command-line-argument]
> mm/swap.c:637:2: error: implicit declaration of function
> 'mlock_page_drain' [-Werror,-Wimplicit-function-declaration]
>         mlock_page_drain(cpu);
>         ^
> 1 error generated.
> make[2]: *** [scripts/Makefile.build:289: mm/swap.o] Error 1
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>

Thanks Naresh, Geert had already reported, and SeongJae sent a fix in

https://lore.kernel.org/lkml/20220209094158.21941-2-sj@kernel.org/

Turns out that a !CONFIG_MMU CONFIG_SMP config will need one more stub,
I just sent a v2 update to SJ's patch in that thread.

Hugh

      reply	other threads:[~2022-02-10  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 14:57 mm/munlock: mlock_page() munlock_page() batch by pagevec Naresh Kamboju
2022-02-10  4:49 ` Hugh Dickins [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=5d63a397-96e-7e9a-eb9f-289904f9998@google.com \
    --to=hughd@google$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=apopple@nvidia$(echo .)com \
    --cc=david@redhat$(echo .)com \
    --cc=gthelen@google$(echo .)com \
    --cc=hannes@cmpxchg$(echo .)org \
    --cc=kirill@shutemov$(echo .)name \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lkft-triage@lists$(echo .)linaro.org \
    --cc=mhocko@suse$(echo .)com \
    --cc=naresh.kamboju@linaro$(echo .)org \
    --cc=regressions@lists$(echo .)linux.dev \
    --cc=riel@surriel$(echo .)com \
    --cc=shakeelb@google$(echo .)com \
    --cc=surenb@google$(echo .)com \
    --cc=vbabka@suse$(echo .)cz \
    --cc=willy@infradead$(echo .)org \
    --cc=yuzhao@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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