From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 12115/12616] mm/page_alloc.c:6244:9: error: too many arguments to function 'cpu_vm_stats_fold'
Date: Tue, 18 Apr 2023 14:05:23 -0700 [thread overview]
Message-ID: <20230418140523.1f4f34f1e30c4ce938a462e9@linux-foundation.org> (raw)
In-Reply-To: <202304190402.keC5huSY-lkp@intel.com>
On Wed, 19 Apr 2023 04:55:24 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 4aa1da8d99724f6c0b762b58a71cee7c5e2e109b
> commit: 938b4fea29fd04e2e7dc7fbb15bacedeafaa765d [12115/12616] vmstat: add pcp remote node draining via cpu_vm_stats_fold
> config: i386-randconfig-a016-20211118 (https://download.01.org/0day-ci/archive/20230419/202304190402.keC5huSY-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=938b4fea29fd04e2e7dc7fbb15bacedeafaa765d
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 938b4fea29fd04e2e7dc7fbb15bacedeafaa765d
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=i386 olddefconfig
> make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202304190402.keC5huSY-lkp@intel.com/
>
> Note: the linux-next/master HEAD 4aa1da8d99724f6c0b762b58a71cee7c5e2e109b builds fine.
> It may have been fixed somewhere.
Indeed, it's fixed in the very next patch,
"vmstat-add-pcp-remote-node-draining-via-cpu_vm_stats_fold-fix".
prev parent reply other threads:[~2023-04-18 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 20:55 kernel test robot
2023-04-18 21:05 ` 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=20230418140523.1f4f34f1e30c4ce938a462e9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mtosatti@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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