From: kbuild test robot <fengguang.wu@intel.com>
To: Al Cooper <alcooperx@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Alban Bedel <albeu@free.fr>, Alex Elder <elder@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Avi Fishman <avifishman70@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, Dmitry Osipenko <digetx@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Hans de Goede <hdegoede@redhat.com>,
James Hogan <jhogan@kernel.org>, Johan Hovold <johan@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-usb@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Rishabh Bhatnagar <rishabhb@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>, Roger Quadros <rogerq@ti.com>
Subject: usb: host: fix platform_no_drv_owner.cocci warnings
Date: Sat, 10 Nov 2018 13:48:46 +0800 [thread overview]
Message-ID: <20181110054846.GA16550@lkp-hsx03> (raw)
From: kbuild test robot <fengguang.wu@intel.com>
drivers/usb/host/ehci-brcm.c:258:3-8: No need to set .owner here. The core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Fixes: 51b4c79a49f1 ("usb: host: Add ability to build new Broadcom STB USB drivers")
CC: Al Cooper <alcooperx@gmail.com>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
url: https://github.com/0day-ci/linux/commits/Al-Cooper/Add-XHCI-EHCI-and-OHCI-support-for-Broadcom-STB-SoS-s/20181110-065441
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
ehci-brcm.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/usb/host/ehci-brcm.c
+++ b/drivers/usb/host/ehci-brcm.c
@@ -255,7 +255,6 @@ static struct platform_driver ehci_brcm_
.remove = ehci_brcm_remove,
.shutdown = usb_hcd_platform_shutdown,
.driver = {
- .owner = THIS_MODULE,
.name = "ehci-brcm",
.pm = &ehci_brcm_pm_ops,
.of_match_table = brcm_ehci_of_match,
reply other threads:[~2018-11-10 5:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181110054846.GA16550@lkp-hsx03 \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=albeu@free.fr \
--cc=alcooperx@gmail.com \
--cc=arnd@arndb.de \
--cc=avifishman70@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bjorn.andersson@linaro.org \
--cc=chunfeng.yun@mediatek.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=elder@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=hdegoede@redhat.com \
--cc=jhogan@kernel.org \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=mchehab+samsung@kernel.org \
--cc=rishabhb@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
/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