netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Latypov <dlatypov@google.com>, Jason@zx2c4.com
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Daniel Latypov <dlatypov@google.com>,
	Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH] wireguard: convert selftest/{counter,ratelimiter}.c to KUnit
Date: Tue, 20 Oct 2020 10:56:21 +0800	[thread overview]
Message-ID: <202010201020.ziddTsOt-lkp@intel.com> (raw)
In-Reply-To: <20201019202431.3472335-1-dlatypov@google.com>

[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]

Hi Daniel,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on 7cf726a59435301046250c42131554d9ccc566b8]

url:    https://github.com/0day-ci/linux/commits/Daniel-Latypov/wireguard-convert-selftest-counter-ratelimiter-c-to-KUnit/20201020-042650
base:    7cf726a59435301046250c42131554d9ccc566b8
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/7a0f82af0af9735a7f20ef9e291e704aff218e8f
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Daniel-Latypov/wireguard-convert-selftest-counter-ratelimiter-c-to-KUnit/20201020-042650
        git checkout 7a0f82af0af9735a7f20ef9e291e704aff218e8f
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   ld: drivers/net/wireguard/receive.o: in function `kunit_test_suites_init':
>> receive.c:(.init.text+0x0): multiple definition of `init_module'; drivers/net/wireguard/main.o:main.c:(.init.text+0x0): first defined here
   ld: drivers/net/wireguard/receive.o: in function `kunit_test_suites_exit':
>> receive.c:(.exit.text+0x0): multiple definition of `cleanup_module'; drivers/net/wireguard/main.o:main.c:(.exit.text+0x0): first defined here
   ld: drivers/net/wireguard/ratelimiter.o: in function `kunit_test_suites_init':
   ratelimiter.c:(.init.text+0x0): multiple definition of `init_module'; drivers/net/wireguard/main.o:main.c:(.init.text+0x0): first defined here
   ld: drivers/net/wireguard/ratelimiter.o: in function `kunit_test_suites_exit':
   ratelimiter.c:(.exit.text+0x0): multiple definition of `cleanup_module'; drivers/net/wireguard/main.o:main.c:(.exit.text+0x0): first defined here

---
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: 77541 bytes --]

  parent reply	other threads:[~2020-10-20  2:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 20:24 [PATCH] wireguard: convert selftest/{counter,ratelimiter}.c to KUnit Daniel Latypov
2020-10-19 22:36 ` Jason A. Donenfeld
2020-10-19 23:30   ` Daniel Latypov
2020-10-20  2:56 ` kernel test robot [this message]
2020-10-20  4:43 ` kernel test robot

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=202010201020.ziddTsOt-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jason@zx2c4.com \
    --cc=brendanhiggins@google.com \
    --cc=dlatypov@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).