From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <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, Yosry Ahmed <yosryahmed@google.com>
Subject: Re: mmotm 2022-02-01-16-04 uploaded (mm/memcontrol.c)
Date: Tue, 1 Feb 2022 19:49:36 -0800 [thread overview]
Message-ID: <46e56d44-bd7d-9239-a5db-099b6e285bee@infradead.org> (raw)
In-Reply-To: <20220202000522.A3834C340EB@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On 2/1/22 16:05, Andrew Morton wrote:
> The mm-of-the-moment snapshot 2022-02-01-16-04 has been uploaded to
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
on i386:
(memcg-add-per-memcg-total-kernel-memory-stat.patch)
../mm/memcontrol.c: In function ‘uncharge_batch’:
../mm/memcontrol.c:6805:4: error: implicit declaration of function ‘mem_cgroup_kmem_record’; did you mean ‘mem_cgroup_id_remove’? [-Werror=implicit-function-declaration]
mem_cgroup_kmem_record(ug->memcg, -ug->nr_kmem);
^~~~~~~~~~~~~~~~~~~~~~
mem_cgroup_id_remove
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r2141.gz --]
[-- Type: application/gzip, Size: 33290 bytes --]
next prev parent reply other threads:[~2022-02-02 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 0:05 mmotm 2022-02-01-16-04 uploaded Andrew Morton
2022-02-02 3:49 ` Randy Dunlap [this message]
2022-02-02 16:39 ` mmotm 2022-02-01-16-04 uploaded (mm/memcontrol.c) Yosry Ahmed
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=46e56d44-bd7d-9239-a5db-099b6e285bee@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 \
--cc=yosryahmed@google.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).