From: lkp@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: rk808: fix platform_no_drv_owner.cocci warnings
Date: Fri, 15 Apr 2016 18:36:11 +0800 [thread overview]
Message-ID: <20160415103611.GA101947@xian> (raw)
In-Reply-To: <1460711790-22646-4-git-send-email-w.egorov@phytec.de>
drivers/regulator/rk8xx-regulator.c:617: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: Wadim Egorov <w.egorov@phytec.de>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
rk8xx-regulator.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/regulator/rk8xx-regulator.c
+++ b/drivers/regulator/rk8xx-regulator.c
@@ -614,7 +614,6 @@ static struct platform_driver rk8xx_regu
.probe = rk8xx_regulator_probe,
.driver = {
.name = "rk8xx-regulator",
- .owner = THIS_MODULE,
},
};
next prev parent reply other threads:[~2016-04-15 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 9:16 [PATCH 0/6] Add RK818 PMIC support Wadim Egorov
2016-04-15 9:16 ` [PATCH 1/6] mfd: RK808: Make RK808 generic, rename rk808.c to rk8xx.c Wadim Egorov
2016-04-15 9:16 ` [PATCH 2/6] mfd: RK808: Add RK818 support Wadim Egorov
2016-04-15 9:16 ` [PATCH 3/6] regulator: rk808: Make rk808 generic, rename rk808-regulator.c Wadim Egorov
2016-04-15 10:26 ` Mark Brown
2016-04-15 16:24 ` Alexandre Belloni
2016-04-18 7:25 ` Wadim Egorov
2016-04-18 17:03 ` Mark Brown
2016-04-15 10:36 ` kbuild test robot [this message]
2016-04-15 10:36 ` kbuild test robot
2016-04-15 9:16 ` [PATCH 4/6] regulator: rk8xx: Migrate to regulator core's simplified DT parsing code Wadim Egorov
2016-04-15 9:16 ` [PATCH 5/6] regulator: rk8xx: Add regulator driver for RK818 Wadim Egorov
2016-04-15 9:16 ` [PATCH 6/6] mfd: dt-bindings: Add RK818 device tree bindings document Wadim Egorov
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=20160415103611.GA101947@xian \
--to=lkp@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 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).