From: Richard Weinberger <richard@nod.at>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Thomas Meyer <thomas@m3y3r.de>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'
Date: Sun, 24 Sep 2017 09:50:44 +0200 [thread overview]
Message-ID: <2167351.jWLNKQ5Lcf@blindfold> (raw)
In-Reply-To: <201709241403.aJtYpMmZ%fengguang.wu@intel.com>
Am Sonntag, 24. September 2017, 08:42:06 CEST schrieb kbuild test robot:
> Hi Thomas,
>
> FYI, the error/warning still remains.
Thomas' fix will be part of the next pull request.
Thanks,
//richard
next prev parent reply other threads:[~2017-09-24 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 6:42 (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add' kbuild test robot
2017-09-24 7:50 ` Richard Weinberger [this message]
2017-09-26 19:37 ` [PATCH] gcov: GCOV_KERNEL and GCOV are mutually exclusive Thomas Meyer
-- strict thread matches above, loose matches on Subject: below --
2017-10-22 4:02 (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add' kbuild test robot
2017-10-15 6:49 kbuild test robot
2017-09-17 18:52 kbuild test robot
2017-09-18 16:32 ` Thomas Meyer
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=2167351.jWLNKQ5Lcf@blindfold \
--to=richard@nod.at \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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