From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2021-03-11-21-46 uploaded (mm/shmem.c)
Date: Fri, 12 Mar 2021 09:14:45 -0800 [thread overview]
Message-ID: <9bbbddbb-3288-a58e-673d-c81cb4bece99@infradead.org> (raw)
In-Reply-To: <20210312054723.MFl9RDDIt%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]
On 3/11/21 9:47 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-03-11-21-46 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 x86_64 or i386 or uml (arch/um/):
../mm/shmem.c:2365:12: warning: ‘enum mcopy_atomic_mode’ declared inside parameter list will not be visible outside of this definition or declaration
enum mcopy_atomic_mode mode, struct page **pagep)
^~~~~~~~~~~~~~~~~
../mm/shmem.c:2365:30: error: parameter 6 (‘mode’) has incomplete type
enum mcopy_atomic_mode mode, struct page **pagep)
^~~~
../mm/shmem.c:2362:5: error: function declaration isn’t a prototype [-Werror=strict-prototypes]
int shmem_mcopy_atomic_pte(struct mm_struct *dst_mm, pmd_t *dst_pmd,
^~~~~~~~~~~~~~~~~~~~~~
CC arch/x86/kernel/cpu/mtrr/generic.o
../mm/shmem.c: In function ‘shmem_mcopy_atomic_pte’:
../mm/shmem.c:2367:30: error: ‘MCOPY_ATOMIC_CONTINUE’ undeclared (first use in this function); did you mean ‘__ATOMIC_CONSUME’?
bool is_continue = (mode == MCOPY_ATOMIC_CONTINUE);
^~~~~~~~~~~~~~~~~~~~~
__ATOMIC_CONSUME
../mm/shmem.c:2367:30: note: each undeclared identifier is reported only once for each function it appears in
CC arch/x86/crypto/twofish_glue_3way.o
../mm/shmem.c:2394:15: error: ‘MCOPY_ATOMIC_NORMAL’ undeclared (first use in this function); did you mean ‘MCOPY_ATOMIC_CONTINUE’?
if (mode == MCOPY_ATOMIC_NORMAL) { /* mcopy_atomic */
^~~~~~~~~~~~~~~~~~~
MCOPY_ATOMIC_CONTINUE
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r8222.gz --]
[-- Type: application/gzip, Size: 27588 bytes --]
prev parent reply other threads:[~2021-03-12 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 5:47 mmotm 2021-03-11-21-46 uploaded akpm
2021-03-12 17:14 ` Randy Dunlap [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=9bbbddbb-3288-a58e-673d-c81cb4bece99@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 \
/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).