From: kbuild test robot <lkp@intel•com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Cc: devicetree@vger•kernel.org,
Felipe Balbi <felipe.balbi@linux•intel.com>,
linux-usb@vger•kernel.org, linux-kernel@vger•kernel.org,
Matthias Brugger <matthias.bgg@gmail•com>,
linux-mediatek@lists•infradead.org, kbuild-all@01•org,
Chunfeng Yun <chunfeng.yun@mediatek•com>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] USB: move usb debugfs directory creation to the usb common core
Date: Wed, 5 Jun 2019 15:20:03 +0800 [thread overview]
Message-ID: <201906051516.NnSFwPqo%lkp@intel.com> (raw)
In-Reply-To: <20190604093258.GB30054@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Hi Greg,
I love your patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v5.2-rc3 next-20190604]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/USB-move-usb-debugfs-directory-creation-to-the-usb-common-core/20190605-114326
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel•com>
All errors (new ones prefixed by >>):
drivers/usb/common/led.o: In function `ledtrig_usb_exit':
>> led.c:(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/usb/common/common.o:common.c:(.text+0x518): first defined here
drivers/usb/common/led.o: In function `ledtrig_usb_init':
>> led.c:(.init.text+0x0): multiple definition of `init_module'
drivers/usb/common/common.o:common.c:(.text+0x4dc): first defined here
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 52829 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-05 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 9:32 [PATCH] USB: move usb debugfs directory creation to the usb common core Greg Kroah-Hartman
2019-06-04 11:59 ` Greg Kroah-Hartman
2019-06-05 2:15 ` Chunfeng Yun
2019-06-05 7:50 ` Chunfeng Yun
2019-06-05 8:52 ` Greg Kroah-Hartman
2019-06-04 12:25 ` Felipe Balbi
2019-06-04 12:43 ` Greg Kroah-Hartman
2019-06-05 7:28 ` Felipe Balbi
2019-06-05 8:37 ` Chunfeng Yun
2019-06-05 7:20 ` 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=201906051516.NnSFwPqo%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=chunfeng.yun@mediatek$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=felipe.balbi@linux$(echo .)intel.com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=matthias.bgg@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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