From: fengguang.wu@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: sirf: fix platform_no_drv_owner.cocci warnings
Date: Thu, 15 Jan 2015 17:05:44 +0800 [thread overview]
Message-ID: <20150115090544.GA9368@waimea> (raw)
In-Reply-To: <201501151731.Zwvnv4Cu%fengguang.wu@intel.com>
sound/soc/sirf/sirf-atlas7-cs42xx8.c:192: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: Yibo Cai <yibo.cai@csr.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
sirf-atlas7-cs42xx8.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/sirf/sirf-atlas7-cs42xx8.c
+++ b/sound/soc/sirf/sirf-atlas7-cs42xx8.c
@@ -189,7 +189,6 @@ MODULE_DEVICE_TABLE(of, sirf_hdmi_card_o
static struct platform_driver sirf_hdmi_card_driver = {
.driver = {
.name = "sirf-hdmi-card",
- .owner = THIS_MODULE,
.pm = &snd_soc_pm_ops,
.of_match_table = sirf_hdmi_card_of_match,
},
next parent reply other threads:[~2015-01-15 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201501151731.Zwvnv4Cu%fengguang.wu@intel.com>
2015-01-15 9:05 ` kbuild test robot [this message]
2015-01-15 9:13 ` [alsa-devel] [PATCH] ASoC: sirf: fix platform_no_drv_owner.cocci warnings Barry Song
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=20150115090544.GA9368@waimea \
--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).