From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [linux-next:master] BUILD REGRESSION 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d
Date: Sat, 22 May 2021 11:29:47 -0700 [thread overview]
Message-ID: <20210522112947.5a5116759db138f32f36d151@linux-foundation.org> (raw)
In-Reply-To: <60a91db6.v1iiGnzpw2gTf48Z%lkp@intel.com>
On Sat, 22 May 2021 23:05:26 +0800 kernel test robot <lkp@intel.com> wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d Add linux-next specific files for 20210521
>
> mm/mremap.c:306:8: warning: variable 'pud' set but not used [-Wunused-but-set-variable]
>
> ...
>
> |-- arm64-randconfig-r014-20210521
> | |-- kernel-kallsyms.c:warning:no-previous-prototype-for-kallsyms_lookup_buildid
> | `-- mm-mremap.c:warning:variable-pud-set-but-not-used
>
> ...
>
> |-- i386-allmodconfig
> | |-- drivers-net-wireless-ath-ath10k-htt_rx.c:warning:variable-more_frags-set-but-not-used
> | |-- kernel-kallsyms.c:warning:no-previous-prototype-for-kallsyms_lookup_buildid
> | `-- mm-mremap.c:warning:variable-pud-set-but-not-used
>
I can't reproduce this. move_normal_pud() does
pud_populate(mm, new_pud, (pmd_t *)pud_page_vaddr(pud));
and I can't see a version of pud_page_vaddr() which doesn't reference its
argument.
Maybe it was fixed since this release of next.
next prev parent reply other threads:[~2021-05-22 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 15:05 kernel test robot
2021-05-22 18:29 ` Andrew Morton [this message]
2021-05-23 8:34 ` Chen, Rong A
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=20210522112947.5a5116759db138f32f36d151@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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