From: kbuild test robot <fengguang.wu@intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: kbuild-all@01.org, Lars Poeschel <poeschel@lemonage.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [wsa:i2c/quirks 10/11] drivers/i2c/busses/i2c-viperboard.c:357:27: sparse: symbol 'vprbrd_quirks' was not declared. Should it be static?
Date: Fri, 9 Jan 2015 02:07:53 +0800 [thread overview]
Message-ID: <201501090239.gPJgrJIE%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux i2c/quirks
head: b1d39af8ae21f4930854b0656aa83a83fd38049e
commit: 5f7099010eda61b777ba84cf9b64dc8428846d25 [10/11] i2c: viperboard: make use of the new infrastructure for quirks
reproduce:
# apt-get install sparse
git checkout 5f7099010eda61b777ba84cf9b64dc8428846d25
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
drivers/i2c/busses/i2c-viperboard.c:128:35: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:128:35: expected unsigned short [unsigned] [usertype] addr
drivers/i2c/busses/i2c-viperboard.c:128:35: got restricted __le16 [usertype] <noident>
drivers/i2c/busses/i2c-viperboard.c:201:34: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:201:34: expected unsigned short [unsigned] [usertype] tf1
drivers/i2c/busses/i2c-viperboard.c:201:34: got restricted __le16 [usertype] <noident>
drivers/i2c/busses/i2c-viperboard.c:202:34: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:202:34: expected unsigned short [unsigned] [usertype] tf2
drivers/i2c/busses/i2c-viperboard.c:202:34: got restricted __le16 [usertype] <noident>
drivers/i2c/busses/i2c-viperboard.c:237:35: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:237:35: expected unsigned short [unsigned] [usertype] addr
drivers/i2c/busses/i2c-viperboard.c:237:35: got restricted __le16 [usertype] <noident>
drivers/i2c/busses/i2c-viperboard.c:300:35: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:300:35: expected unsigned short [unsigned] [usertype] len
drivers/i2c/busses/i2c-viperboard.c:300:35: got restricted __le16 [usertype] <noident>
drivers/i2c/busses/i2c-viperboard.c:325:35: sparse: incorrect type in assignment (different base types)
drivers/i2c/busses/i2c-viperboard.c:325:35: expected unsigned short [unsigned] [usertype] len
drivers/i2c/busses/i2c-viperboard.c:325:35: got restricted __le16 [usertype] <noident>
>> drivers/i2c/busses/i2c-viperboard.c:357:27: sparse: symbol 'vprbrd_quirks' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
next reply other threads:[~2015-01-08 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:07 kbuild test robot [this message]
2015-01-08 18:07 ` [PATCH wsa] i2c: viperboard: vprbrd_quirks can be static kbuild test robot
2015-01-08 18:38 ` [wsa:i2c/quirks 10/11] drivers/i2c/busses/i2c-viperboard.c:357:27: sparse: symbol 'vprbrd_quirks' was not declared. Should it be static? 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=201501090239.gPJgrJIE%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poeschel@lemonage.de \
--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