Hi Wolfram,
On Tue, Jul 11, 2017 at 08:54:31AM +0200, Wolfram Sang wrote:
On Tue, Jul 11, 2017 at 12:16:34PM +0800, kbuild test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-4.13
head: 8f1a357d41a22009150cf404b5aa5876efdb59b1
commit: d44005672d83f89d7d797efc490a751a696e7d91 [15/51] i2c: stub: fix build warning regression
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout d44005672d83f89d7d797efc490a751a696e7d91
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>> warning: __mcount_loc already exists: drivers/i2c/algos/i2c-algo-bit.o
--
>> warning: __mcount_loc already exists: drivers/i2c/busses/i2c-emev2.o
--
>> warning: __mcount_loc already exists: drivers/i2c/busses/i2c-xlp9xx.o
--
>> warning: __mcount_loc already exists: drivers/i2c/busses/i2c-rcar.o
False positive? How can a commit that only touches the DEBUG define in
i2c-algo-bit have effects on the latter three drivers?
You are right, I just confirmed that it's a false positive.
The bisect didn't run distclean, which may explain the warnings on
duplicate __mcount_loc.
Cheers,
Fengguang
