From: kbuild test robot <lkp@intel.com>
To: Nicolas Saenz Julienne <nicolassaenzj@gmail.com>
Cc: kbuild-all@01.org, linus.walleij@linaro.org, gnurou@gmail.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] gpio: fix platform_no_drv_owner.cocci warnings
Date: Mon, 12 Oct 2015 01:12:20 +0800 [thread overview]
Message-ID: <20151011171220.GA93323@lkp-ib04.intel.com> (raw)
In-Reply-To: <1444581663-31066-1-git-send-email-nicolassaenzj@gmail.com>
drivers/gpio/gpio-tps65218.c:153: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: Nicolas Saenz Julienne <nicolassaenzj@gmail.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
gpio-tps65218.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/gpio/gpio-tps65218.c
+++ b/drivers/gpio/gpio-tps65218.c
@@ -150,7 +150,6 @@ MODULE_DEVICE_TABLE(of, tps65218_dt_matc
static struct platform_driver tps65218_gpio_driver = {
.driver = {
.name = "tps65218-gpio",
- .owner = THIS_MODULE,
.of_match_table = of_match_ptr(tps65218_dt_match)
},
.probe = tps65218_gpio_probe,
next prev parent reply other threads:[~2015-10-11 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 16:41 [PATCH] gpio: add tps65218 gpio driver Nicolas Saenz Julienne
2015-10-11 17:12 ` kbuild test robot [this message]
2015-10-11 17:12 ` kbuild test robot
2015-10-16 20:26 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2022-05-03 10:00 [asahilinux:bits/110-smc 3/14] drivers/gpio/gpio-macsmc.c:230:3-8: No need to set .owner here. The core will do it kernel test robot
2022-05-03 9:53 ` [PATCH] gpio: fix platform_no_drv_owner.cocci warnings kernel test robot
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 ` [PATCH] gpio: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-10-16 14:47 ` Linus Walleij
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=20151011171220.GA93323@lkp-ib04.intel.com \
--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=nicolassaenzj@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
all inboxes | Powered by JetHome®