From: Kees Cook <keescook@chromium.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: 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
Subject: Re: mmotm 2020-06-25-20-36 uploaded (mm/slab.c)
Date: Fri, 26 Jun 2020 13:02:54 -0700 [thread overview]
Message-ID: <202006261302.13BB6AB703@keescook> (raw)
In-Reply-To: <7ff248c7-d447-340c-a8e2-8c02972aca70@infradead.org>
On Fri, Jun 26, 2020 at 09:28:36AM -0700, Randy Dunlap wrote:
> On 6/25/20 8:37 PM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2020-06-25-20-36 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for mm-of-the-moment:
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > more than once a week.
>
>
> when CONFIG_NUMA is not set/enabled:
>
> ../mm/slab.c: In function ‘___cache_free’:
> ../mm/slab.c:3471:2: error: implicit declaration of function ‘__free_one’; did you mean ‘__free_page’? [-Werror=implicit-function-declaration]
> __free_one(ac, objp);
> ^~~~~~~~~~
Eek! Thanks for catching that. I will send a fix patch.
--
Kees Cook
next prev parent reply other threads:[~2020-06-26 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 3:37 mmotm 2020-06-25-20-36 uploaded akpm
2020-06-26 16:28 ` mmotm 2020-06-25-20-36 uploaded (mm/slab.c) Randy Dunlap
2020-06-26 20:02 ` Kees Cook [this message]
2020-06-26 22:09 ` mmotm 2020-06-25-20-36 uploaded (mm/memory-failure.c) Randy Dunlap
2020-06-27 3:41 ` Andrew Morton
2020-06-26 23:35 ` mmotm 2020-06-25-20-36 uploaded (objtool warning) Randy Dunlap
2020-06-30 9:59 ` Peter Zijlstra
2020-06-30 15:29 ` Randy Dunlap
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=202006261302.13BB6AB703@keescook \
--to=keescook@chromium.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=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).