From: kbuild test robot <lkp@intel.com>
To: richard.dorsch@gmail.com
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
lm-sensors@lm-sensors.org, linux-i2c@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-gpio@vger.kernel.org,
lee.jones@linaro.org, jdelvare@suse.com, linux@roeck-us.net,
wim@iguana.be, jo.sunga@advantech.com,
Richard Vidal-Dorsch <richard.dorsch@gmail.com>
Subject: [PATCH] fix platform_no_drv_owner.cocci warnings
Date: Sat, 9 Jan 2016 08:50:04 +0800 [thread overview]
Message-ID: <20160109005004.GA58406@roam> (raw)
In-Reply-To: <1452292166-20118-3-git-send-email-richard.dorsch@gmail.com>
drivers/gpio/imanager-gpio.c:170: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
CC: Richard Vidal-Dorsch <richard.dorsch@gmail.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
imanager-gpio.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/gpio/imanager-gpio.c
+++ b/drivers/gpio/imanager-gpio.c
@@ -167,7 +167,6 @@ static int imanager_remove(struct platfo
static struct platform_driver imanager_gpio_driver = {
.driver = {
- .owner = THIS_MODULE,
.name = "imanager_gpio",
},
.probe = imanager_gpio_probe,
next prev parent reply other threads:[~2016-01-09 0:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 22:29 [PATCH 0/6] Add Advantech iManager EC driver set richard.dorsch
2016-01-08 22:29 ` [PATCH 1/6] Add Advantech iManager MFD core driver richard.dorsch
2016-01-08 22:29 ` [PATCH 2/6] Add Advantech iManager GPIO driver richard.dorsch
2016-01-09 0:50 ` kbuild test robot
2016-01-10 7:42 ` [PATCH 7/8] Remove .owner from platform_driver struct richard.dorsch
2016-01-09 0:50 ` kbuild test robot [this message]
2016-01-08 22:29 ` [PATCH 3/6] Add Advantech iManager HWmon driver richard.dorsch
2016-01-08 22:29 ` [PATCH 4/6] Add Advantech iManager I2C driver richard.dorsch
2016-01-08 22:29 ` [PATCH 5/6] Add Advantech iManager Backlight driver richard.dorsch
2016-01-08 22:29 ` [PATCH 6/6] Add Advantech iManager Watchdog driver richard.dorsch
2016-01-09 2:02 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-09 2:02 ` [PATCH 6/6] Add Advantech iManager Watchdog driver kbuild test robot
2016-01-10 7:42 ` [PATCH 8/8] Remove .owner from platform_driver struct richard.dorsch
[not found] <201906240241.S3kwAGar%lkp@intel.com>
2019-06-23 18:50 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2017-02-20 12:05 [PATCH 1/2] add driver for cypress cy8cmbr3102 kbuild test robot
2017-02-20 10:33 ` Patrick Vogelaar
2017-02-20 12:05 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-11-23 18:13 [PATCH] ALSA SoC MAX98927 driver - Initial release kbuild test robot
2016-11-23 4:57 ` Ryan Lee
2016-11-23 18:13 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-07-27 14:41 Julia Lawall
2016-08-08 5:47 ` Vinod Koul
2016-02-15 7:34 [media 7/7] PCI bridge driver for PT3 & PXQ3PE kbuild test robot
2016-02-15 6:08 ` info
2016-02-15 7:34 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:44 [PATCH v2 5/6] Add Advantech iManager Backlight driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:44 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:34 [PATCH v2 4/6] Add Advantech iManager I2C driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:34 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:25 [PATCH v2 3/6] Add Advantech iManager HWmon driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:25 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:11 [PATCH v2 1/6] Add Advantech iManager MFD core driver kbuild test robot
2016-01-10 9:10 ` richard.dorsch
2016-01-10 10:11 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
[not found] <201503291519.K9Z6Qptb%fengguang.wu@intel.com>
2015-03-29 7:49 ` kbuild test robot
2015-03-30 13:05 ` Thierry Reding
2015-04-07 13:09 ` Linus Walleij
2015-04-08 1:24 ` Fengguang Wu
[not found] <201503291545.My1tADgz%fengguang.wu@intel.com>
2015-03-29 7:42 ` kbuild test robot
2015-03-29 16:27 ` Mark Brown
[not found] <201503291531.GP28FwKy%fengguang.wu@intel.com>
2015-03-29 7:33 ` kbuild test robot
2015-03-29 16:24 ` Mark Brown
2015-03-30 12:52 ` Thierry Reding
[not found] <201502131224.TGzEj1Ve%fengguang.wu@intel.com>
2015-02-13 4:49 ` kbuild test robot
[not found] <201501160912.S502Nlmz%fengguang.wu@intel.com>
2015-01-16 1:06 ` kbuild test robot
2015-03-11 11:05 ` Thierry Reding
2015-03-18 1:38 ` Linus Walleij
2015-03-24 10:43 ` Thierry Reding
2015-03-25 1:56 ` Fengguang Wu
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=20160109005004.GA58406@roam \
--to=lkp@intel.com \
--cc=jdelvare@suse.com \
--cc=jo.sunga@advantech.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=richard.dorsch@gmail.com \
--cc=wim@iguana.be \
/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).