From: Wolfram Sang <wsa@the-dreams.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Lee Jones <lee.jones@linaro.org>,
Octavian Purdila <octavian.purdila@intel.com>,
Johan Hovold <johan@kernel.org>,
Laurentiu Palcu <laurentiu.palcu@intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [wsa:i2c/quirks 8/11] drivers/i2c/busses/i2c-dln2.c:184:27: sparse: symbol 'dln2_i2c_quirks' was not declared. Should it be static?
Date: Thu, 8 Jan 2015 19:37:48 +0100 [thread overview]
Message-ID: <20150108183748.GB29629@katana> (raw)
In-Reply-To: <201501090243.rmSyDkOe%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Fri, Jan 09, 2015 at 02:02:00AM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux i2c/quirks
> head: b1d39af8ae21f4930854b0656aa83a83fd38049e
> commit: dfd33ddaa80259918c200cfacb9076c75cf1da82 [8/11] i2c: dln2: make use of the new infrastructure for quirks
> reproduce:
> # apt-get install sparse
> git checkout dfd33ddaa80259918c200cfacb9076c75cf1da82
> make ARCH=x86_64 allmodconfig
> make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
> >> drivers/i2c/busses/i2c-dln2.c:184:27: sparse: symbol 'dln2_i2c_quirks' was not declared. Should it be static?
>
> Please review and possibly fold the followup patch.
Development branch noise, please ignore.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-01-08 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:02 [wsa:i2c/quirks 8/11] drivers/i2c/busses/i2c-dln2.c:184:27: sparse: symbol 'dln2_i2c_quirks' was not declared. Should it be static? kbuild test robot
2015-01-08 18:02 ` [PATCH wsa] i2c: dln2: dln2_i2c_quirks can be static kbuild test robot
2015-01-08 18:37 ` Wolfram Sang [this message]
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=20150108183748.GB29629@katana \
--to=wsa@the-dreams.de \
--cc=fengguang.wu@intel.com \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=laurentiu.palcu@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.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;
as well as URLs for NNTP newsgroup(s).