From: kbuild test robot <lkp@intel.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
ohad@wizery.com, bjorn.andersson@linaro.org
Cc: kbuild-all@lists.01.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] rpmsg: core: Add support to retrieve name extension
Date: Sun, 3 May 2020 00:18:58 +0800 [thread overview]
Message-ID: <202005030022.RmcTuEkL%lkp@intel.com> (raw)
In-Reply-To: <20200501204950.18629-3-mathieu.poirier@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
Hi Mathieu,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on linux/master v5.7-rc3 next-20200501]
[cannot apply to rpmsg/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Mathieu-Poirier/rpmsg-core-Add-support-for-name-extension/20200502-050248
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 052c467cb58748e302a95546925928e637025acc
config: x86_64-fedora-25 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/net/wireless/ath/wcn36xx/smd.o: in function `rpmsg_device_get_name_extension':
>> include/linux/rpmsg.h:250: multiple definition of `rpmsg_device_get_name_extension'; drivers/net/wireless/ath/wcn36xx/main.o:include/linux/rpmsg.h:250: first defined here
vim +250 include/linux/rpmsg.h
247
248 const char *rpmsg_device_get_name_extension(struct rpmsg_device *dev,
249 unsigned int skip)
> 250 {
251 /* This shouldn't be possible */
252 WARN_ON(1);
253
254 return NULL;
255 }
256
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 52636 bytes --]
prev parent reply other threads:[~2020-05-02 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:49 [PATCH v3 0/2] rpmsg: core: Add support for name extension Mathieu Poirier
2020-05-01 20:49 ` [PATCH v3 1/2] rpmsg: core: Add wildcard match for name service Mathieu Poirier
2020-05-01 20:49 ` [PATCH v3 2/2] rpmsg: core: Add support to retrieve name extension Mathieu Poirier
2020-05-02 16:18 ` kbuild test robot [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=202005030022.RmcTuEkL%lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.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).