From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [linux-next:master 8148/8790] fs/proc/task_mmu.c:2105:17: error: implicit declaration of function 'pagemap_scan_backout_range'; did you mean 'pagemap_scan_push_range'?
Date: Sun, 1 Oct 2023 12:47:06 -0700 [thread overview]
Message-ID: <20231001124706.85ae33038ed93000ec8a8871@linux-foundation.org> (raw)
In-Reply-To: <202310011545.iHTT4Y7S-lkp@intel.com>
On Sun, 1 Oct 2023 15:50:38 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: df964ce9ef9fea10cf131bf6bad8658fde7956f6
> commit: 588d06cd90cfb015926def2469ab99f3c72a205d [8148/8790] fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix-2
> config: x86_64-randconfig-005-20231001 (https://download.01.org/0day-ci/archive/20231001/202310011545.iHTT4Y7S-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231001/202310011545.iHTT4Y7S-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202310011545.iHTT4Y7S-lkp@intel.com/
>
> Note: the linux-next/master HEAD df964ce9ef9fea10cf131bf6bad8658fde7956f6 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> fs/proc/task_mmu.c: In function 'pagemap_scan_thp_entry':
> >> fs/proc/task_mmu.c:2105:17: error: implicit declaration of function 'pagemap_scan_backout_range'; did you mean 'pagemap_scan_push_range'? [-Werror=implicit-function-declaration]
> 2105 | pagemap_scan_backout_range(p, start, end);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | pagemap_scan_push_range
Thanks. Seems this was fixed in a later fix.
fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes.patch
fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix.patch
fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix-fix.patch
you are here -> fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix-2.patch
fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix-3.patch
fs-proc-task_mmu-implement-ioctl-to-get-and-optionally-clear-info-about-ptes-fix-3-fix.patch
prev parent reply other threads:[~2023-10-01 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 7:50 kernel test robot
2023-10-01 19:47 ` Andrew Morton [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=20231001124706.85ae33038ed93000ec8a8871@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=usama.anjum@collabora.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