From: kbuild test robot <fengguang.wu@intel.com>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: kbuild-all@01.org, mturquette@baylibre.com, sboyd@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com, lee.jones@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org,
mazziesaccount@gmail.com, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
mikko.mutanen@fi.rohmeurope.com,
heikki.haikola@fi.rohmeurope.com
Subject: [PATCH] clk: bd71837: fix platform_no_drv_owner.cocci warnings
Date: Sun, 27 May 2018 16:28:22 +0800 [thread overview]
Message-ID: <20180527082822.GA26026@lkp-ne04> (raw)
In-Reply-To: <20180524055955.GH4249@localhost.localdomain>
From: kbuild test robot <fengguang.wu@intel.com>
drivers/clk/clk-bd71837.c:145:6-11: 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: 0e03c7b6a3c7 ("clk: bd71837: Build ROHM BD71837 PMIC clock driver")
CC: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
clk-bd71837.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/clk/clk-bd71837.c
+++ b/drivers/clk/clk-bd71837.c
@@ -142,7 +142,6 @@ static int bd71837_clk_remove(struct pla
static struct platform_driver bd71837_clk = {
.driver = {
.name = "bd71837-clk",
- .owner = THIS_MODULE,
},
.probe = bd71837_clk_probe,
.remove = bd71837_clk_remove,
next prev parent reply other threads:[~2018-05-27 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 5:59 [PATCH 7/9] clk: bd71837: Build ROHM BD71837 PMIC clock driver Matti Vaittinen
2018-05-27 8:28 ` kbuild test robot [this message]
2018-05-27 8:28 ` 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=20180527082822.GA26026@lkp-ne04 \
--to=fengguang.wu@intel.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mikko.mutanen@fi.rohmeurope.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).