From: Wolfram Sang <wsa@the-dreams.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: linux-i2c@vger.kernel.org,
Wolfram Sang <wsa-dev@sang-engineering.com>,
kbuild-all@01.org, Philip Li <philip.li@intel.com>
Subject: Re: [kbuild-all] [wsa:i2c/for-4.13 15/51] warning: __mcount_loc already exists: drivers/i2c/algos/i2c-algo-bit.o
Date: Tue, 11 Jul 2017 10:46:19 +0200 [thread overview]
Message-ID: <20170711084619.GD2342@katana> (raw)
In-Reply-To: <20170711075555.e5ktanutreueotu7@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
> >>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.
Cool. Thanks for the heads up!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-07-11 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 4:16 [wsa:i2c/for-4.13 15/51] warning: __mcount_loc already exists: drivers/i2c/algos/i2c-algo-bit.o kbuild test robot
2017-07-11 6:54 ` Wolfram Sang
2017-07-11 7:55 ` [kbuild-all] " Fengguang Wu
2017-07-11 8:46 ` Wolfram Sang [this message]
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=20170711084619.GD2342@katana \
--to=wsa@the-dreams.de \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=wsa-dev@sang-engineering.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 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.