From: fengguang.wu@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: sunxi: fix platform_no_drv_owner.cocci warnings
Date: Thu, 17 Sep 2015 04:55:55 +0800 [thread overview]
Message-ID: <20150916205555.GA207987@athens> (raw)
In-Reply-To: <201509170447.vzyqPoy7%fengguang.wu@intel.com>
sound/soc/sunxi/sun4i-codec.c:708: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: Emilio L?pez <emilio@elopez.com.ar>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
sun4i-codec.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/sunxi/sun4i-codec.c
+++ b/sound/soc/sunxi/sun4i-codec.c
@@ -705,7 +705,6 @@ static int sun4i_codec_remove(struct pla
static struct platform_driver sun4i_codec_driver = {
.driver = {
.name = "sun4i-codec",
- .owner = THIS_MODULE,
.of_match_table = sun4i_codec_of_match,
},
.probe = sun4i_codec_probe,
next parent reply other threads:[~2015-09-16 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201509170447.vzyqPoy7%fengguang.wu@intel.com>
2015-09-16 20:55 ` kbuild test robot [this message]
2015-09-17 13:32 ` [PATCH] ASoC: sunxi: fix platform_no_drv_owner.cocci warnings Maxime Ripard
2015-09-30 18:26 [PATCH v2 4/4] ASOC: sunxi: Add support for the spdif block kbuild test robot
2015-09-30 17:50 ` codekipper at gmail.com
2015-09-30 18:26 ` [PATCH] ASOC: sunxi: fix platform_no_drv_owner.cocci warnings kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 16:01 [PATCH v3 2/2] ASOC: sunxi: Add support for the SPDIF block kbuild test robot
2016-02-02 14:49 ` codekipper at gmail.com
2016-02-02 16:01 ` [PATCH] ASOC: sunxi: 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=20150916205555.GA207987@athens \
--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).