From: kbuild test robot <lkp@intel.com>
To: Raul E Rangel <rrangel@chromium.org>
Cc: kbuild-all@01.org, linux-usb@vger.kernel.org,
groeck@chromium.org, oneukum@suse.com, djkurtz@chromium.org,
zwisler@chromium.org, Raul E Rangel <rrangel@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Dmitry Torokhov <dtor@chromium.org>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [PATCH v3] usb/hcd: Send a uevent signaling that the host controller had died
Date: Fri, 19 Apr 2019 04:59:26 +0800 [thread overview]
Message-ID: <201904190446.57TY0W6W%lkp@intel.com> (raw)
In-Reply-To: <20190417190316.10032-1-rrangel@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2851 bytes --]
Hi Raul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v5.1-rc5 next-20190418]
[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/Raul-E-Rangel/usb-hcd-Send-a-uevent-signaling-that-the-host-controller-had-died/20190419-033556
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: i386-randconfig-x014-201915 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from include/linux/srcu.h:21:0,
from include/linux/notifier.h:16,
from include/linux/memory_hotplug.h:7,
from include/linux/mmzone.h:749,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from drivers/usb/core/hcd.c:13:
drivers/usb/core/hcd.c: In function '__usb_create_hcd':
>> drivers/usb/core/hcd.c:2566:29: error: 'hcd_died_work' undeclared (first use in this function); did you mean 'schedule_work'?
INIT_WORK(&hcd->died_work, hcd_died_work);
^
include/linux/workqueue.h:245:20: note: in definition of macro '__INIT_WORK'
(_work)->func = (_func); \
^~~~~
>> drivers/usb/core/hcd.c:2566:2: note: in expansion of macro 'INIT_WORK'
INIT_WORK(&hcd->died_work, hcd_died_work);
^~~~~~~~~
drivers/usb/core/hcd.c:2566:29: note: each undeclared identifier is reported only once for each function it appears in
INIT_WORK(&hcd->died_work, hcd_died_work);
^
include/linux/workqueue.h:245:20: note: in definition of macro '__INIT_WORK'
(_work)->func = (_func); \
^~~~~
>> drivers/usb/core/hcd.c:2566:2: note: in expansion of macro 'INIT_WORK'
INIT_WORK(&hcd->died_work, hcd_died_work);
^~~~~~~~~
vim +2566 drivers/usb/core/hcd.c
2565
> 2566 INIT_WORK(&hcd->died_work, hcd_died_work);
2567
2568 hcd->driver = driver;
2569 hcd->speed = driver->flags & HCD_MASK;
2570 hcd->product_desc = (driver->product_desc) ? driver->product_desc :
2571 "USB Host Controller";
2572 return hcd;
2573 }
2574 EXPORT_SYMBOL_GPL(__usb_create_hcd);
2575
---
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: 29985 bytes --]
next prev parent reply other threads:[~2019-04-18 20:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 19:03 [v3] usb/hcd: Send a uevent signaling that the host controller had died Raul E Rangel
2019-04-17 19:03 ` [PATCH v3] " Raul E Rangel
2019-04-18 20:59 ` kbuild test robot [this message]
2019-04-18 21:35 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2019-04-17 19:14 [v3] " Alan Stern
2019-04-17 19:14 ` [PATCH v3] " Alan Stern
2019-04-17 20:20 [v3] " Raul E Rangel
2019-04-17 20:20 ` [PATCH v3] " Raul Rangel
2019-04-17 20:39 [v3] " Alan Stern
2019-04-17 20:39 ` [PATCH v3] " Alan Stern
2019-04-17 22:10 [v3] " Raul E Rangel
2019-04-17 22:10 ` [PATCH v3] " Raul Rangel
2019-04-17 22:23 [v3] " Guenter Roeck
2019-04-17 22:23 ` [PATCH v3] " Guenter Roeck
2019-04-17 22:41 [v3] " Raul E Rangel
2019-04-17 22:41 ` [PATCH v3] " Raul Rangel
2019-04-17 23:20 [v3] " Guenter Roeck
2019-04-17 23:20 ` [PATCH v3] " Guenter Roeck
2019-04-18 6:51 [v3] " Greg Kroah-Hartman
2019-04-18 6:51 ` [PATCH v3] " Greg Kroah-Hartman
2019-04-18 14:21 [v3] " Alan Stern
2019-04-18 14:21 ` [PATCH v3] " Alan Stern
2019-04-18 14:30 [v3] " Greg Kroah-Hartman
2019-04-18 14:30 ` [PATCH v3] " Greg Kroah-Hartman
2019-04-18 15:29 [v3] " Raul E Rangel
2019-04-18 15:29 ` [PATCH v3] " Raul Rangel
2019-04-19 12:16 [v3] " Greg Kroah-Hartman
2019-04-19 12:16 ` [PATCH v3] " Greg Kroah-Hartman
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=201904190446.57TY0W6W%lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=djkurtz@chromium.org \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mathias.nyman@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=oneukum@suse.com \
--cc=rrangel@chromium.org \
--cc=stern@rowland.harvard.edu \
--cc=zwisler@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.