All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [wsa:i2c/for-next 89/93] m68k-linux-ld: i2c-mt65xx.c:undefined reference to `__divdi3'
Date: Sat, 16 May 2020 06:06:26 +0800	[thread overview]
Message-ID: <202005160623.knS7RLFO%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
head:   41895bfee70e7b8a5af7deae458fbf02c1fe782a
commit: 5f1ae73d538a84f96f53c2381b50bc278181136c [89/93] i2c: mediatek: Add i2c ac-timing adjust support
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 5f1ae73d538a84f96f53c2381b50bc278181136c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=m68k 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

m68k-linux-ld: drivers/i2c/busses/i2c-mt65xx.o: in function `mtk_i2c_calculate_speed':
i2c-mt65xx.c:(.text+0x532): undefined reference to `__divdi3'
>> m68k-linux-ld: i2c-mt65xx.c:(.text+0x57e): undefined reference to `__divdi3'
m68k-linux-ld: i2c-mt65xx.c:(.text+0x5c0): undefined reference to `__divdi3'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 54280 bytes --]

                 reply	other threads:[~2020-05-15 22:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202005160623.knS7RLFO%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.