From: kbuild test robot <lkp@intel.com>
To: Daniel Campello <campello@chromium.org>
Cc: kbuild-all@lists.01.org, LKML <linux-kernel@vger.kernel.org>,
Daniel Campello <campello@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Enrico Granata <egranata@chromium.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Andreas Klinger <ak@it-klinger.de>,
linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH v2] iio: Add SEMTECH SX9310/9311 sensor driver
Date: Mon, 10 Feb 2020 00:47:28 +0800 [thread overview]
Message-ID: <202002100001.BwAzqv0v%lkp@intel.com> (raw)
In-Reply-To: <20200206121647.1.I1f56fe698017f22d6e825c913c256d5afc2ad69f@changeid>
Hi Daniel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on iio/togreg]
[also build test WARNING on linux/master linus/master v5.5 next-20200207]
[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/Daniel-Campello/iio-Add-SEMTECH-SX9310-9311-sensor-driver/20200209-180706
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-162-g98276e61-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/iio/proximity/sx9310.c:184:9: sparse: sparse: Using plain integer as NULL pointer
drivers/iio/proximity/sx9310.c:185:9: sparse: sparse: Using plain integer as NULL pointer
drivers/iio/proximity/sx9310.c:186:9: sparse: sparse: Using plain integer as NULL pointer
vim +184 drivers/iio/proximity/sx9310.c
162
163 #define SX9310_CHANNEL(idx, name) \
164 { \
165 .type = IIO_PROXIMITY, \
166 .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \
167 .info_mask_shared_by_all = BIT(IIO_CHAN_INFO_SAMP_FREQ), \
168 .indexed = 1, \
169 .channel = idx, \
170 .extend_name = name, \
171 .address = SX9310_REG_DIFF_MSB, \
172 .event_spec = sx9310_events, \
173 .num_event_specs = ARRAY_SIZE(sx9310_events), \
174 .scan_index = idx, \
175 .scan_type = { \
176 .sign = 's', \
177 .realbits = 12, \
178 .storagebits = 16, \
179 .endianness = IIO_BE, \
180 }, \
181 }
182
183 static const struct iio_chan_spec sx9310_channels[] = {
> 184 SX9310_CHANNEL(0, 0), /* CS0 */
185 SX9310_CHANNEL(1, 0), /* CS1 */
186 SX9310_CHANNEL(2, 0), /* CS2 */
187 SX9310_CHANNEL(3, "COMB"), /* COMB */
188
189 IIO_CHAN_SOFT_TIMESTAMP(4),
190 };
191
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
prev parent reply other threads:[~2020-02-09 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 19:20 Daniel Campello
2020-02-09 16:47 ` kbuild test robot [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=202002100001.BwAzqv0v%lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@it-klinger.de \
--cc=campello@chromium.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=egranata@chromium.org \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®