From: kbuild test robot <lkp@intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 3/3] s390: char: make slp_ctl explicitly non-modular
Date: Sun, 30 Oct 2016 06:49:52 +0800 [thread overview]
Message-ID: <201610300612.yagUIBR9%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161029203843.515-4-paul.gortmaker@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2118 bytes --]
Hi Paul,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/Paul-Gortmaker/lightnvm-make-core-c-explicitly-non-modular/20161030-044459
config: s390-default_defconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390
All error/warnings (new ones prefixed by >>):
>> drivers/s390/char/sclp_ctl.c:129:1: warning: data definition has no type or storage class
builtin_misc_device(sclp_ctl_device);
^~~~~~~~~~~~~~~~~~~
>> drivers/s390/char/sclp_ctl.c:129:1: error: type defaults to 'int' in declaration of 'builtin_misc_device' [-Werror=implicit-int]
>> drivers/s390/char/sclp_ctl.c:129:1: warning: parameter names (without types) in function declaration
>> drivers/s390/char/sclp_ctl.c:124:26: warning: 'sclp_ctl_device' defined but not used [-Wunused-variable]
static struct miscdevice sclp_ctl_device = {
^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +129 drivers/s390/char/sclp_ctl.c
118 .llseek = no_llseek,
119 };
120
121 /*
122 * Misc device definition
123 */
> 124 static struct miscdevice sclp_ctl_device = {
125 .minor = MISC_DYNAMIC_MINOR,
126 .name = "sclp",
127 .fops = &sclp_ctl_fops,
128 };
> 129 builtin_misc_device(sclp_ctl_device);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 16407 bytes --]
next prev parent reply other threads:[~2016-10-29 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 20:38 [PATCH 0/3] Add new builtin_misc_device users Paul Gortmaker
2016-10-29 20:38 ` [PATCH 3/3] s390: char: make slp_ctl explicitly non-modular Paul Gortmaker
2016-10-29 22:49 ` kbuild test robot [this message]
2016-10-30 13:43 ` Martin Schwidefsky
2016-10-30 16:04 ` Paul Gortmaker
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=201610300612.yagUIBR9%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=schwidefsky@de.ibm.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