From: kbuild test robot <lkp@intel.com>
To: Rama Krishna Phani A <rphani@codeaurora.org>
Cc: kbuild-all@01.org, linux-iio@vger.kernel.org, jic23@kernel.org,
linux-arm-msm@vger.kernel.org, smohanad@codeaurora.org,
mgautam@codeaurora.org,
Rama Krishna Phani A <rphani@codeaurora.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Julia Lawall <Julia.Lawall@lip6.fr>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1]iio: adc: spmi-vadc: Changes to support different scaling
Date: Wed, 2 Nov 2016 15:25:11 +0800 [thread overview]
Message-ID: <201611021525.CyIcgfld%fengguang.wu@intel.com> (raw)
In-Reply-To: <1477373226-29587-1-git-send-email-rphani@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]
Hi Rama,
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Rama-Krishna-Phani-A/iio-adc-spmi-vadc-Changes-to-support-different-scaling/20161025-141253
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: openrisc-allmodconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All warnings (new ones prefixed by >>):
drivers/iio/adc/qcom-spmi-vadc.c: In function 'vadc_scale_fn':
>> drivers/iio/adc/qcom-spmi-vadc.c:632:4: warning: comparison of distinct pointer types lacks a cast
drivers/iio/adc/qcom-spmi-vadc.c:646:4: warning: comparison of distinct pointer types lacks a cast
vim +632 drivers/iio/adc/qcom-spmi-vadc.c
616 int ret;
617
618 switch (prop->scale_function) {
619
620 case SCALE_DEFAULT:
621 vadc_scale_calib(vadc, adc_code, prop, &voltage);
622
623 prescale = &vadc_prescale_ratios[prop->prescale];
624 voltage = voltage * prescale->den;
625 return div64_s64(voltage, prescale->num);
626
627 case SCALE_THERM_100K_PULLUP:
628 case SCALE_XOTHERM:
629 vadc_scale_calib(vadc, adc_code, prop, &voltage);
630
631 if (prop->calibration == VADC_CALIB_ABSOLUTE)
> 632 do_div(voltage, 1000);
633
634 vadc_map_voltage_temp(adcmap_100k_104ef_104fb,
635 ARRAY_SIZE(adcmap_100k_104ef_104fb),
636 voltage, &result);
637 result *= 1000;
638 return result;
639
640 case SCALE_PMIC_THERM:
---
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: 38716 bytes --]
prev parent reply other threads:[~2016-11-02 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 5:27 Rama Krishna Phani A
2016-10-25 13:09 ` Sricharan
2016-10-26 9:27 ` Phani A, Rama Krishna
2016-10-26 10:17 ` Sricharan
2016-10-26 10:45 ` Phani A, Rama Krishna
2016-11-02 7:25 ` 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=201611021525.CyIcgfld%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=pmeerw@pmeerw.net \
--cc=rphani@codeaurora.org \
--cc=smohanad@codeaurora.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 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®