On Fri, 6 Sep 2019 16:58:52 +0800 "Chen, Rong A" <rong.a.c...@intel.com> wrote:
> On 9/5/2019 5:08 PM, Jonathan Cameron wrote: > > On Wed, 4 Sep 2019 15:37:11 +0300 > > Andy Shevchenko <andriy.shevche...@linux.intel.com> wrote: > > > >> On Wed, Sep 04, 2019 at 11:33:50AM +0800, kbuild test robot wrote: > >>> tree: > >>> https://kernel.googlesource.com/pub/scm/linux/kernel/git/gregkh/staging.git > >>> staging-testing > >>> head: 74eb9c06b1d722468db397595ac6834b9e4ac235 > >>> commit: 473d12f7638c93acbd9296a8cd455b203d5eb528 [314/401] iio: > >>> hid-sensor-attributes: Convert to use int_pow() > >>> config: i386-randconfig-e004-201935 (attached as .config) > >>> compiler: gcc-7 (Debian 7.4.0-11) 7.4.0 > >>> reproduce: > >>> git checkout 473d12f7638c93acbd9296a8cd455b203d5eb528 > >>> # save the attached .config to linux build tree > >>> make ARCH=i386 > >>> > >>> If you fix the issue, kindly add following tag > >>> Reported-by: kbuild test robot <l...@intel.com> > >>> > >>> All errors (new ones prefixed by >>): > >> So, as far as I understood it wasn't compiled on 32-bit before, so, it's > >> not a > >> new error and thus would (has to?) be fixed separately. > > I'm not convinced. My assumption is this is triggered because the local > > pow_10 > > function was returning int whereas generic int_pow is returning an int64. > > Whilst I would imagine it is fairly easy to fix, I'll not have a chance to > > do > > so until the weekend. Perhaps we should just revert this patch and revisit > > in the next cycle? > > > > 0-day people, any idea why the iio.git/testing branch isn't getting built > > any > > more? I got lazy and started relying on your infrastructure and not > > bothering > > with 32 bit local builds. Somewhere along the way you stopped building it > > and I'm afraid I didn't really notice. > > > > Thanks for you all your hard work on 0day btw as it used to catch a lot > > of stuff my local few builds didn't! > > > > Jonathan > > Hi Jonathan, > > Sorry for the inconvenience, we updated the git url to > https://kernel.googlesource.com/pub/scm/linux/kernel/git/jic23/iio.git > recently, > but it seems the branches are not updated, so we switch to use > https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git now. Thanks. I wonder why some trees don't seem to be getting updated in that google mirror. Anyone know who manages that as a bit silly having mirrors that are years out of date. Anyone know who manages those mirrors? I've poked the send feedback form but who knows if it'll filter through to the right person. Anyhow, thanks Rong Chen. Looking forwards to continuing to be lazy and rely on your excellent service! Jonathan > > Best Regards, > Rong Chen > > > > > > > > > >>> ld: drivers/iio/common/hid-sensors/hid-sensor-attributes.o: in > >>> function `adjust_exponent_nano': > >>>>> drivers/iio/common/hid-sensors/hid-sensor-attributes.c:312: undefined > >>>>> reference to `__udivdi3' > >>>>> ld: drivers/iio/common/hid-sensors/hid-sensor-attributes.c:314: > >>>>> undefined reference to `__umoddi3' > >>>>> ld: drivers/iio/common/hid-sensors/hid-sensor-attributes.c:324: > >>>>> undefined reference to `__udivdi3' > >>> ld: drivers/iio/common/hid-sensors/hid-sensor-attributes.c:325: > >>> undefined reference to `__umoddi3' > >> > > > > _______________________________________________ > > kbuild-all mailing list > > kbuild-...@lists.01.org > > https://lists.01.org/mailman/listinfo/kbuild-all > _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
