From: Wolfram Sang <wsa@the-dreams.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Wolfram Sang <wsa-dev@sang-engineering.com>,
kbuild-all@01.org, linux-i2c@vger.kernel.org
Subject: Re: [wsa:i2c/for-4.13 15/51] warning: __mcount_loc already exists: drivers/i2c/algos/i2c-algo-bit.o
Date: Tue, 11 Jul 2017 08:54:31 +0200 [thread overview]
Message-ID: <20170711065431.GA2342@katana> (raw)
In-Reply-To: <201707111232.THY3DhFS%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-11 6:54 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 [this message]
2017-07-11 7:55 ` [kbuild-all] " Fengguang Wu
2017-07-11 8:46 ` Wolfram Sang
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=20170711065431.GA2342@katana \
--to=wsa@the-dreams.de \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-i2c@vger.kernel.org \
--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 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).