From: kbuild test robot <lkp@intel.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: kbuild-all@lists.01.org, Linux I2C <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 3/4] i2c: smbus: Add a way to instantiate SPD EEPROMs automatically
Date: Mon, 14 Oct 2019 18:21:50 +0800 [thread overview]
Message-ID: <201910141823.bXxWHSkl%lkp@intel.com> (raw)
In-Reply-To: <20191014113950.1f989ba6@endymion>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Hi Jean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.4-rc3 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Jean-Delvare/Instantiate-SPD-EEPROMs-at-boot-on-x86/20191014-174252
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/i2c/i2c-core-base.c:24:0:
include/linux/i2c-smbus.h: In function 'i2c_register_spd':
>> include/linux/i2c-smbus.h:52:9: warning: 'return' with a value, in function returning void
return 0;
^
include/linux/i2c-smbus.h:50:13: note: declared here
static void i2c_register_spd(struct i2c_adapter *adap)
^~~~~~~~~~~~~~~~
In file included from drivers/i2c/i2c-core-base.c:24:0:
At top level:
include/linux/i2c-smbus.h:50:13: warning: 'i2c_register_spd' defined but not used [-Wunused-function]
vim +/return +52 include/linux/i2c-smbus.h
46
47 #if IS_ENABLED(CONFIG_I2C_SMBUS) && IS_ENABLED(CONFIG_DMI)
48 void i2c_register_spd(struct i2c_adapter *adap);
49 #else
50 static void i2c_register_spd(struct i2c_adapter *adap)
51 {
> 52 return 0;
53 }
54 #endif
55
---
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: 59081 bytes --]
next prev parent reply other threads:[~2019-10-14 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 9:36 [PATCH 0/4] Instantiate SPD EEPROMs at boot on x86 Jean Delvare
2019-10-14 9:38 ` [PATCH 1/4] firmware: dmi: Remember the memory type Jean Delvare
2019-10-14 9:38 ` [PATCH 2/4] firmware: dmi: Add dmi_memdev_handle Jean Delvare
2019-10-14 9:39 ` [PATCH 3/4] i2c: smbus: Add a way to instantiate SPD EEPROMs automatically Jean Delvare
2019-10-14 10:21 ` kbuild test robot [this message]
2019-10-14 14:55 ` Jean Delvare
2019-10-14 9:41 ` [PATCH 4/4] i2c: i801: Instantiate " Jean Delvare
2019-10-14 10:22 ` kbuild test robot
2019-10-14 18:02 ` Jean Delvare
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=201910141823.bXxWHSkl%lkp@intel.com \
--to=lkp@intel.com \
--cc=jdelvare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).