From: kbuild test robot <lkp@intel.com>
To: Shuming Fan <shumingf@realtek.com>
Cc: kbuild-all@01.org, alsa-devel@alsa-project.org,
Mark Brown <broonie@kernel.org>, Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] ASoC: rt1305: fix platform_no_drv_owner.cocci warnings
Date: Tue, 17 Apr 2018 03:41:24 +0800 [thread overview]
Message-ID: <20180416194124.GA75306@lkp-hsx02> (raw)
In-Reply-To: <201804170321.o4jkfmnc%fengguang.wu@intel.com>
From: Fengguang Wu <fengguang.wu@intel.com>
sound/soc/codecs/rt1305.c:1174: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
Fixes: 29bc643ddd7e ("ASoC: rt1305: Add RT1305/RT1306 amplifier driver")
CC: Shuming Fan <shumingf@realtek.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
rt1305.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/codecs/rt1305.c
+++ b/sound/soc/codecs/rt1305.c
@@ -1171,7 +1171,6 @@ static void rt1305_i2c_shutdown(struct i
static struct i2c_driver rt1305_i2c_driver = {
.driver = {
.name = "rt1305",
- .owner = THIS_MODULE,
#if defined(CONFIG_OF)
.of_match_table = rt1305_of_match,
#endif
next prev parent reply other threads:[~2018-04-16 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 19:41 [asoc:for-4.18 35/37] sound/soc/codecs/rt1305.c:1179:23: error: implicit declaration of function 'ACPI_PTR'; did you mean 'ERR_PTR'? kbuild test robot
2018-04-16 19:41 ` kbuild test robot [this message]
2018-04-17 10:30 ` Applied "ASoC: rt1305: fix platform_no_drv_owner.cocci warnings" to the asoc tree Mark Brown
2018-04-17 10:32 ` Mark Brown
2018-04-17 11:29 ` Mark Brown
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=20180416194124.GA75306@lkp-hsx02 \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=shumingf@realtek.com \
--cc=tiwai@suse.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