From: fengguang.wu@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: rockchip: fix platform_no_drv_owner.cocci warnings
Date: Wed, 26 Aug 2015 19:48:13 +0800 [thread overview]
Message-ID: <20150826114813.GA88839@ivytown2> (raw)
In-Reply-To: <201508261911.CXlWEwle%fengguang.wu@intel.com>
sound/soc/rockchip/rockchip_rt5645.c:214: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: zhengxing <zhengxing@rock-chips.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
rockchip_rt5645.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/rockchip/rockchip_rt5645.c
+++ b/sound/soc/rockchip/rockchip_rt5645.c
@@ -211,7 +211,6 @@ static struct platform_driver snd_rk_mc_
.probe = snd_rk_mc_probe,
.driver = {
.name = DRV_NAME,
- .owner = THIS_MODULE,
.pm = &snd_soc_pm_ops,
.of_match_table = rockchip_rt5645_of_match,
},
next parent reply other threads:[~2015-08-26 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201508261911.CXlWEwle%fengguang.wu@intel.com>
2015-08-26 11:48 ` kbuild test robot [this message]
[not found] <201508261907.XaXhY7JN%fengguang.wu@intel.com>
2015-08-26 11:44 ` [PATCH] ASoC: rockchip: 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=20150826114813.GA88839@ivytown2 \
--to=fengguang.wu@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).