From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [wsa:i2c/for-5.8 98/102] drivers/i2c/busses/i2c-npcm7xx.c:127:11: sparse: sparse: symbol 'npcm_i2caddr' was not declared. Should it be
Date: Thu, 11 Jun 2020 10:50:34 +0800 [thread overview]
Message-ID: <202006111013.sWdCKUu7%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-5.8
head: cb301414763e07e4cef58c9d5ef3750d1f9539bc
commit: f54736925a4f83a67588381d0ead69d19323b526 [98/102] i2c: npcm7xx: Add support for slave mode for Nuvoton
config: i386-randconfig-s001-20200611 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-247-gcadbd124-dirty
git checkout f54736925a4f83a67588381d0ead69d19323b526
# save the attached .config to linux build tree
make W=1 C=1 ARCH=i386 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/i2c/busses/i2c-npcm7xx.c:127:11: sparse: sparse: symbol 'npcm_i2caddr' was not declared. Should it be static?
>> drivers/i2c/busses/i2c-npcm7xx.c:1115:61: sparse: sparse: Using plain integer as NULL pointer
Please review and possibly fold the followup patch.
---
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: 41767 bytes --]
next reply other threads:[~2020-06-11 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 2:50 kernel test robot [this message]
2020-06-11 2:50 ` [RFC PATCH wsa] i2c: npcm7xx: npcm_i2caddr[] can be static kernel test robot
2020-06-11 10:31 ` Wolfram Sang
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=202006111013.sWdCKUu7%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.