From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: kbuild test robot <lkp@intel.com>, Qii Wang <qii.wang@mediatek.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [wsa:i2c/for-next] BUILD REGRESSION 41895bfee70e7b8a5af7deae458fbf02c1fe782a
Date: Mon, 18 May 2020 12:48:51 +0200 [thread overview]
Message-ID: <20200518104851.GE3268@ninjato> (raw)
In-Reply-To: <5ebf3670.uIi3PwYqAckNzmnl%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 7810 bytes --]
Adding patch author to CC.
Hi Qii Wang,
can you send an incremental patch to replace the 64-bit division with
either do_div() or some apropriate div64_* function?
While there, it might also be good to double check if the divisor is
always non-zero to prevent "division by zero" OOPSes, if you haven't
done this already.
Thanks,
Wolfram
On Sat, May 16, 2020 at 08:40:16AM +0800, kbuild test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
> branch HEAD: 41895bfee70e7b8a5af7deae458fbf02c1fe782a Merge branch 'i2c/for-current-fixed' into i2c/for-next
>
> Error/Warning in current branch:
>
> arm-linux-gnueabi-ld: i2c-mt65xx.c:(.text+0xa34): undefined reference to `__aeabi_ldivmod'
> i2c-mt65xx.c:(.text+0x3e5): undefined reference to `__divdi3'
> i2c-mt65xx.c:(.text+0x532): undefined reference to `__divdi3'
> i2c-mt65xx.c:(.text+0x5d2): undefined reference to `__divdi3'
> i2c-mt65xx.c:(.text+0x9ac): undefined reference to `__aeabi_ldivmod'
> i2c-mt65xx.c:(.text.mtk_i2c_calculate_speed+0x2d4): undefined reference to `__divdi3'
> ld: i2c-mt65xx.c:(.text+0x60f): undefined reference to `__divdi3'
> m68k-linux-ld: i2c-mt65xx.c:(.text+0x57e): undefined reference to `__divdi3'
> mips-linux-ld: i2c-mt65xx.c:(.text.mtk_i2c_calculate_speed+0x368): undefined reference to `__divdi3'
>
> Error/Warning ids grouped by kconfigs:
>
> recent_errors
> |-- arm-allyesconfig
> | |-- arm-linux-gnueabi-ld:i2c-mt65xx.c:(.text):undefined-reference-to-__aeabi_ldivmod
> | `-- i2c-mt65xx.c:(.text):undefined-reference-to-__aeabi_ldivmod
> |-- h8300-allyesconfig
> | `-- i2c-mt65xx.c:(.text):undefined-reference-to-__divdi3
> |-- i386-allyesconfig
> | |-- i2c-mt65xx.c:(.text):undefined-reference-to-__divdi3
> | `-- ld:i2c-mt65xx.c:(.text):undefined-reference-to-__divdi3
> |-- m68k-allyesconfig
> | |-- i2c-mt65xx.c:(.text):undefined-reference-to-__divdi3
> | `-- m68k-linux-ld:i2c-mt65xx.c:(.text):undefined-reference-to-__divdi3
> `-- mips-allyesconfig
> |-- i2c-mt65xx.c:(.text.mtk_i2c_calculate_speed):undefined-reference-to-__divdi3
> `-- mips-linux-ld:i2c-mt65xx.c:(.text.mtk_i2c_calculate_speed):undefined-reference-to-__divdi3
>
> elapsed time: 482m
>
> configs tested: 109
> configs skipped: 3
>
> arm defconfig
> arm allyesconfig
> arm allmodconfig
> arm allnoconfig
> arm64 allyesconfig
> arm64 defconfig
> arm64 allmodconfig
> arm64 allnoconfig
> sparc allyesconfig
> m68k allyesconfig
> mips allyesconfig
> arm at91_dt_defconfig
> arm sama5_defconfig
> arm realview_defconfig
> arm spear13xx_defconfig
> powerpc pq2fads_defconfig
> c6x evmc6678_defconfig
> parisc defconfig
> arm u300_defconfig
> powerpc ps3_defconfig
> arm bcm2835_defconfig
> arm spitz_defconfig
> arm tegra_defconfig
> i386 allyesconfig
> i386 defconfig
> i386 debian-10.3
> i386 allnoconfig
> ia64 allmodconfig
> ia64 defconfig
> ia64 allnoconfig
> ia64 allyesconfig
> m68k allmodconfig
> m68k allnoconfig
> m68k sun3_defconfig
> m68k defconfig
> nios2 defconfig
> nios2 allyesconfig
> openrisc defconfig
> c6x allyesconfig
> c6x allnoconfig
> openrisc allyesconfig
> nds32 defconfig
> nds32 allnoconfig
> csky allyesconfig
> csky defconfig
> alpha defconfig
> alpha allyesconfig
> xtensa allyesconfig
> h8300 allyesconfig
> h8300 allmodconfig
> xtensa defconfig
> arc defconfig
> arc allyesconfig
> sh allmodconfig
> sh allnoconfig
> microblaze allnoconfig
> mips allnoconfig
> mips allmodconfig
> parisc allnoconfig
> parisc allyesconfig
> parisc allmodconfig
> powerpc defconfig
> powerpc allyesconfig
> powerpc rhel-kconfig
> powerpc allmodconfig
> powerpc allnoconfig
> i386 randconfig-a006-20200515
> i386 randconfig-a005-20200515
> i386 randconfig-a003-20200515
> i386 randconfig-a001-20200515
> i386 randconfig-a004-20200515
> i386 randconfig-a002-20200515
> i386 randconfig-a012-20200515
> i386 randconfig-a016-20200515
> i386 randconfig-a014-20200515
> i386 randconfig-a011-20200515
> i386 randconfig-a013-20200515
> i386 randconfig-a015-20200515
> x86_64 randconfig-a005-20200515
> x86_64 randconfig-a003-20200515
> x86_64 randconfig-a006-20200515
> x86_64 randconfig-a004-20200515
> x86_64 randconfig-a001-20200515
> x86_64 randconfig-a002-20200515
> riscv allyesconfig
> riscv allnoconfig
> riscv defconfig
> riscv allmodconfig
> s390 allyesconfig
> s390 allnoconfig
> s390 allmodconfig
> s390 defconfig
> x86_64 defconfig
> sparc defconfig
> sparc64 defconfig
> sparc64 allnoconfig
> sparc64 allyesconfig
> sparc64 allmodconfig
> um allmodconfig
> um allnoconfig
> um allyesconfig
> um defconfig
> x86_64 rhel
> x86_64 rhel-7.6
> x86_64 rhel-7.6-kselftests
> x86_64 rhel-7.2-clear
> x86_64 lkp
> x86_64 fedora-25
> x86_64 kexec
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2020-05-18 10:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5ebf3670.uIi3PwYqAckNzmnl%lkp@intel.com>]
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=20200518104851.GE3268@ninjato \
--to=wsa-dev@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=lkp@intel.com \
--cc=qii.wang@mediatek.com \
/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).