From: David Hildenbrand <david@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [ammarfaizi2-block:akpm/mm/mm-unstable 289/353] mm/debug_vm_pgtable.c:814:43: error: implicit declaration of function 'generic_max_swapfile_size'
Date: Sat, 14 Jan 2023 16:40:47 +0100 [thread overview]
Message-ID: <84c33e13-3a07-b356-5a4a-83b3886be0c3@redhat.com> (raw)
In-Reply-To: <202301141908.5CL5Toth-lkp@intel.com>
On 14.01.23 12:24, kernel test robot wrote:
> tree: https://github.com/ammarfaizi2/linux-block akpm/mm/mm-unstable
> head: b62e8196de8602c16d6ea10807d147b480db2712
> commit: 2234b0437c6fa63c611df1032c614464957e9262 [289/353] mm/debug_vm_pgtable: more pte_swp_exclusive() sanity checks
> config: x86_64-randconfig-a013
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
> # https://github.com/ammarfaizi2/linux-block/commit/2234b0437c6fa63c611df1032c614464957e9262
> git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
> git fetch --no-tags ammarfaizi2-block akpm/mm/mm-unstable
> git checkout 2234b0437c6fa63c611df1032c614464957e9262
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=x86_64 olddefconfig
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> mm/debug_vm_pgtable.c: In function 'pte_swap_exclusive_tests':
>>> mm/debug_vm_pgtable.c:814:43: error: implicit declaration of function 'generic_max_swapfile_size' [-Werror=implicit-function-declaration]
> 814 | unsigned long max_swapfile_size = generic_max_swapfile_size();
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Triggers without CONFIG_SWAP. Will send a fixup.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2023-01-14 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 11:24 kernel test robot
2023-01-14 15:40 ` David Hildenbrand [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=84c33e13-3a07-b356-5a4a-83b3886be0c3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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