From: kbuild test robot <lkp@intel.com>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: kbuild-all@01.org, linus.walleij@linaro.org, gnurou@gmail.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: [PATCH] gpio: fix platform_no_drv_owner.cocci warnings
Date: Wed, 7 Oct 2015 11:14:13 +0800 [thread overview]
Message-ID: <20151007031413.GA12931@roam> (raw)
In-Reply-To: <20151007024018.GA25534@sophia>
drivers/gpio/gpio-104-idio-16.c:151: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: William Breathitt Gray <vilhelm.gray@gmail.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
gpio-104-idio-16.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/gpio/gpio-104-idio-16.c
+++ b/drivers/gpio/gpio-104-idio-16.c
@@ -148,7 +148,6 @@ static struct platform_device *a_104_idi
static struct platform_driver a_104_idio_16_driver = {
.driver = {
.name = "104-idio-16",
- .owner = THIS_MODULE
},
.remove = a_104_idio_16_remove
};
next prev parent reply other threads:[~2015-10-07 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 3:14 [PATCH v4] gpio: Add GPIO support for the ACCES 104-IDIO-16 kbuild test robot
2015-10-07 2:40 ` William Breathitt Gray
2015-10-07 3:14 ` kbuild test robot [this message]
2015-10-16 14:47 ` [PATCH] gpio: fix platform_no_drv_owner.cocci warnings Linus Walleij
2015-10-16 15:47 ` [kbuild-all] " Fengguang Wu
2015-10-16 15:53 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2015-10-11 17:12 [PATCH] gpio: add tps65218 gpio driver kbuild test robot
2015-10-11 16:41 ` Nicolas Saenz Julienne
2015-10-11 17:12 ` [PATCH] gpio: fix platform_no_drv_owner.cocci warnings kbuild 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=20151007031413.GA12931@roam \
--to=lkp@intel.com \
--cc=gnurou@gmail.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vilhelm.gray@gmail.com \
/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).