linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: kbuild-all@01.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [renesas-drivers:topic/clk-r8a77990-z2-v3 11/13] rcar-gen3-cpg.c:undefined reference to `__udivdi3'
Date: Wed, 6 Feb 2019 07:37:37 +0800	[thread overview]
Message-ID: <201902060735.NFAVGNjO%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git topic/clk-r8a77990-z2-v3
head:   3423d0ef4af282d1a1021b40cc2e739c08c9046b
commit: 0961e355977f7806b926ea0ae29c5cffa7867894 [11/13] clk: renesas: rcar-gen3: Support Z and Z2 clocks with high frequency parents
config: i386-allmodconfig (attached as .config)
compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
reproduce:
        git checkout 0961e355977f7806b926ea0ae29c5cffa7867894
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   ld: drivers/clk/renesas/rcar-gen3-cpg.o: in function `cpg_z_clk_set_rate':
>> rcar-gen3-cpg.c:(.text+0x13c): undefined reference to `__udivdi3'

---
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: 66633 bytes --]

             reply	other threads:[~2019-02-05 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 23:37 kbuild test robot [this message]
2019-02-06  7:03 ` [renesas-drivers:topic/clk-r8a77990-z2-v3 11/13] rcar-gen3-cpg.c:undefined reference to `__udivdi3' Geert Uytterhoeven
2019-02-11 12:47   ` Geert Uytterhoeven

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=201902060735.NFAVGNjO%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=kbuild-all@01.org \
    --cc=linux-renesas-soc@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).