From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [peterz-queue:locking/core 1/2] arch/x86/mm/highmem_32.c:66:13: warning: no previous prototype for 'set_highmem_pages_init'
Date: Sat, 01 Aug 2020 04:01:42 +0800 [thread overview]
Message-ID: <202008010432.veKzO2t0%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
head: c4dfe2b515b510d7db6858c14f9b2492130a543b
commit: 589bcab3e46636fc4fb4f56b3f51adba98f50ee0 [1/2] seqlock,headers: Untangle the spaghetti monster
config: i386-randconfig-r001-20200731 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
git checkout 589bcab3e46636fc4fb4f56b3f51adba98f50ee0
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/mm/highmem_32.c:66:13: warning: no previous prototype for 'set_highmem_pages_init' [-Wmissing-prototypes]
66 | void __init set_highmem_pages_init(void)
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/set_highmem_pages_init +66 arch/x86/mm/highmem_32.c
60e64d46a58236 arch/i386/mm/highmem.c Vivek Goyal 2005-06-25 65
867c5b5292583b arch/x86/mm/highmem_32.c Pekka Enberg 2009-03-03 @66 void __init set_highmem_pages_init(void)
:::::: The code at line 66 was first introduced by commit
:::::: 867c5b5292583b1e474cbbcb4c77f09bfca3903c x86: set_highmem_pages_init() cleanup
:::::: TO: Pekka Enberg <penberg@cs.helsinki.fi>
:::::: CC: Ingo Molnar <mingo@elte.hu>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35097 bytes --]
reply other threads:[~2020-07-31 20:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202008010432.veKzO2t0%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.