From: kbuild test robot <fengguang.wu@intel.com>
To: Biao Huang <biao.huang@mediatek.com>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] pinctrl: mediatek: fix platform_no_drv_owner.cocci warnings
Date: Wed, 17 Feb 2016 06:06:15 +0800 [thread overview]
Message-ID: <20160216220615.GA90965@lkp-sb04> (raw)
In-Reply-To: <201602170605.jhwKTr8k%fengguang.wu@intel.com>
drivers/pinctrl/mediatek/pinctrl-mt2701.c:576: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: Biao Huang <biao.huang@mediatek.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
pinctrl-mt2701.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/pinctrl/mediatek/pinctrl-mt2701.c
+++ b/drivers/pinctrl/mediatek/pinctrl-mt2701.c
@@ -573,7 +573,6 @@ static struct platform_driver mtk_pinctr
.probe = mt2701_pinctrl_probe,
.driver = {
.name = "mediatek-mt2701-pinctrl",
- .owner = THIS_MODULE,
.of_match_table = mt2701_pctrl_match,
.pm = &mtk_eint_pm_ops,
},
next parent reply other threads:[~2016-02-16 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201602170605.jhwKTr8k%fengguang.wu@intel.com>
2016-02-16 22:06 ` kbuild test robot [this message]
2016-02-18 23:25 ` [PATCH] pinctrl: mediatek: fix platform_no_drv_owner.cocci warnings Linus Walleij
2021-06-26 5:15 [pinctrl:devel 16/44] drivers/pinctrl/mediatek/pinctrl-mt8365.c:488:3-8: No need to set .owner here. The core will do it kernel test robot
2021-06-26 5:15 ` [PATCH] pinctrl: mediatek: fix platform_no_drv_owner.cocci warnings kernel test robot
2021-07-23 16:11 ` Linus Walleij
[not found] <202107151930.RDfhAWvb-lkp@intel.com>
2021-07-15 11:12 ` kernel 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=20160216220615.GA90965@lkp-sb04 \
--to=fengguang.wu@intel.com \
--cc=biao.huang@mediatek.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yingjoe.chen@mediatek.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).