driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: devel@driverdev.osuosl.org, linux-iio@vger.kernel.org, kbuild-all@01.org
Subject: Re: [kbuild-all] [staging:staging-testing 314/401] drivers/iio/common/hid-sensors/hid-sensor-attributes.c:312: undefined reference to `__udivdi3'
Date: Fri, 6 Sep 2019 16:58:52 +0800	[thread overview]
Message-ID: <3ecfa3de-5f8c-3606-b72a-f767cf646d56@intel.com> (raw)
In-Reply-To: <20190905100846.000045b4@huawei.com>



On 9/5/2019 5:08 PM, Jonathan Cameron wrote:
> On Wed, 4 Sep 2019 15:37:11 +0300
> Andy Shevchenko <andriy.shevchenko@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 <lkp@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.

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-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2019-09-06  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  3:33 [staging:staging-testing 314/401] drivers/iio/common/hid-sensors/hid-sensor-attributes.c:312: undefined reference to `__udivdi3' kbuild test robot
2019-09-04 12:37 ` Andy Shevchenko
2019-09-05  9:08   ` Jonathan Cameron
2019-09-06  8:58     ` Chen, Rong A [this message]
2019-09-06  9:11       ` [kbuild-all] " Jonathan Cameron

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=3ecfa3de-5f8c-3606-b72a-f767cf646d56@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jonathan.cameron@huawei.com \
    --cc=kbuild-all@01.org \
    --cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).