From: Roman Gushchin <guro@fb.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: linux-next: Tree for Aug 20 (mm/memcontrol)
Date: Tue, 20 Aug 2019 16:13:44 +0000 [thread overview]
Message-ID: <20190820161341.GA20702@tower.dhcp.thefacebook.com> (raw)
In-Reply-To: <bcce34db-47ea-cf02-057d-c63c2bf7eeeb@infradead.org>
On Tue, Aug 20, 2019 at 07:59:54AM -0700, Randy Dunlap wrote:
> On 8/20/19 12:09 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190819:
> >
>
> on i386 or x86_64:
>
> ../mm/memcontrol.c: In function ‘__mem_cgroup_free’:
> ../mm/memcontrol.c:4885:2: error: implicit declaration of function ‘memcg_flush_percpu_vmstats’; did you mean ‘qdisc_is_percpu_stats’? [-Werror=implicit-function-declaration]
> memcg_flush_percpu_vmstats(memcg, false);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~
> qdisc_is_percpu_stats
> ../mm/memcontrol.c:4886:2: error: implicit declaration of function ‘memcg_flush_percpu_vmevents’; did you mean ‘memcg_check_events’? [-Werror=implicit-function-declaration]
> memcg_flush_percpu_vmevents(memcg);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> memcg_check_events
>
>
>
> Full i386 randconfig file is attached.
Hi Randy!
The issue has already been fixed ( https://lkml.org/lkml/2019/8/19/1007 ),
and Andrew has picked an updated version to the mm tree.
So it will be resolved soon.
Thanks!
prev parent reply other threads:[~2019-08-20 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 7:09 linux-next: Tree for Aug 20 Stephen Rothwell
2019-08-20 14:59 ` linux-next: Tree for Aug 20 (mm/memcontrol) Randy Dunlap
2019-08-20 16:13 ` Roman Gushchin [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=20190820161341.GA20702@tower.dhcp.thefacebook.com \
--to=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).