From: kernel test robot <lkp@intel.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Heiko Carstens <hca@linux.ibm.com>
Subject: [linux-next:master 5813/6512] arch/s390/kernel/uv.c:423:44: error: 'prot_virt_host' undeclared; did you mean
Date: Wed, 24 Mar 2021 03:41:18 +0800 [thread overview]
Message-ID: <202103240312.0QqewEWu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d949689e7383cd5271470f2b99dbe2fd3199bffd
commit: 37564ed834aca26993b77b9b2a0119ec1ba6e00c [5813/6512] s390/uv: add prot virt guest/host indication files
config: s390-randconfig-r002-20210323 (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=37564ed834aca26993b77b9b2a0119ec1ba6e00c
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 37564ed834aca26993b77b9b2a0119ec1ba6e00c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/s390/kernel/uv.c: In function 'uv_is_prot_virt_host':
>> arch/s390/kernel/uv.c:423:44: error: 'prot_virt_host' undeclared (first use in this function); did you mean 'prot_virt_guest'?
423 | return scnprintf(page, PAGE_SIZE, "%d\n", prot_virt_host);
| ^~~~~~~~~~~~~~
| prot_virt_guest
arch/s390/kernel/uv.c:423:44: note: each undeclared identifier is reported only once for each function it appears in
arch/s390/kernel/uv.c:424:1: error: control reaches end of non-void function [-Werror=return-type]
424 | }
| ^
cc1: some warnings being treated as errors
vim +423 arch/s390/kernel/uv.c
419
420 static ssize_t uv_is_prot_virt_host(struct kobject *kobj,
421 struct kobj_attribute *attr, char *page)
422 {
> 423 return scnprintf(page, PAGE_SIZE, "%d\n", prot_virt_host);
424 }
425
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 20026 bytes --]
reply other threads:[~2021-03-23 19:42 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=202103240312.0QqewEWu-lkp@intel.com \
--to=lkp@intel.com \
--cc=frankja@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).