From: Arnd Bergmann <arnd@arndb.de>
Cc: Yang Shi <yang.shi@linux.alibaba.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>, Hugh Dickins <hughd@google.com>,
Shakeel Butt <shakeelb@google.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Roman Gushchin <guro@fb.com>, Chris Down <chris@chrisdown.name>,
Yafang Shao <laoar.shao@gmail.com>,
Mel Gorman <mgorman@techsingularity.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] vmscan: fix memcg_kmem build failure
Date: Mon, 8 Jul 2019 15:27:45 +0200 [thread overview]
Message-ID: <CAK8P3a2pn4s1aLWAd+riKHO9RGgu20u=62Ds1fWg1OCQEGiiOw@mail.gmail.com> (raw)
In-Reply-To: <20190708124120.3400683-1-arnd@arndb.de>
On Mon, Jul 8, 2019 at 2:42 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> When CONFIG_MEMCG_KMEM is disabled, we get a build failure
> for calling a nonexisting memcg_expand_shrinker_maps():
>
> mm/vmscan.c:220:7: error: implicit declaration of function 'memcg_expand_shrinker_maps' [-Werror,-Wimplicit-function-declaration]
> if (memcg_expand_shrinker_maps(id)) {
> ^
I see now that a fix for this is already in today's linux-next, please ignore
my patch.
Arnd
prev parent reply other threads:[~2019-07-08 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 12:41 [PATCH] vmscan: fix memcg_kmem build failure Arnd Bergmann
2019-07-08 13:27 ` Arnd Bergmann [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='CAK8P3a2pn4s1aLWAd+riKHO9RGgu20u=62Ds1fWg1OCQEGiiOw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=chris@chrisdown.name \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=ktkhai@virtuozzo.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.au \
--cc=shakeelb@google.com \
--cc=yang.shi@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;
as well as URLs for NNTP newsgroup(s).