From: kbuild test robot <fengguang.wu@intel.com>
To: Katsuhiro Suzuki <katsuhiro@katsuster.net>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH] ASoC: rockchip: fix platform_no_drv_owner.cocci warnings
Date: Tue, 25 Dec 2018 12:38:26 +0800 [thread overview]
Message-ID: <20181225043826.GA158508@lkp-ib04.lkp.intel.com> (raw)
In-Reply-To: <201812251233.q6697gUW%fengguang.wu@intel.com>
From: kbuild test robot <fengguang.wu@intel.com>
sound/soc/codecs/rk3328_codec.c:508:6-11: 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: dc1b33660692 ("ASoC: rockchip: support ACODEC for rk3328")
CC: Katsuhiro Suzuki <katsuhiro@katsuster.net>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6a1d293238c1774cef23c25b5188b0c134c29a34
commit: dc1b33660692441867a8ec5be147915dfa3bc8cb [11432/12209] ASoC: rockchip: support ACODEC for rk3328
rk3328_codec.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/codecs/rk3328_codec.c
+++ b/sound/soc/codecs/rk3328_codec.c
@@ -505,7 +505,6 @@ MODULE_DEVICE_TABLE(of, rk3328_codec_of_
static struct platform_driver rk3328_codec_driver = {
.driver = {
.name = "rk3328-codec",
- .owner = THIS_MODULE,
.of_match_table = of_match_ptr(rk3328_codec_of_match),
},
.probe = rk3328_platform_probe,
next parent reply other threads:[~2018-12-25 4:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201812251233.q6697gUW%fengguang.wu@intel.com>
2018-12-25 4:38 ` kbuild test robot [this message]
2018-12-31 19:42 ` Applied "ASoC: rockchip: fix platform_no_drv_owner.cocci warnings" to the asoc tree Mark Brown
2018-12-31 19:42 ` Mark Brown
2019-01-04 14:01 ` Mark Brown
2019-01-04 14:01 ` Mark Brown
2019-01-04 17:09 ` Mark Brown
2019-01-04 17:09 ` Mark Brown
2019-01-07 12:30 ` Mark Brown
2019-01-07 12:30 ` Mark Brown
2017-01-23 15:24 [alsa-devel] [PATCH v4 3/4] ASoC: rockchip: Add machine driver for RK3288 boards that use analog/HDMI kbuild test robot
[not found] ` <20170123104149.2508-4-romain.perier-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-01-23 15:24 ` [PATCH] ASoC: rockchip: fix platform_no_drv_owner.cocci warnings kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2015-08-26 11:48 [asoc:topic/rockchip 2/4] sound/soc/rockchip/rockchip_rt5645.c:214:3-8: No need to set .owner here. The core will do it kbuild test robot
2015-08-26 11:48 ` [PATCH] ASoC: rockchip: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-08-26 11:48 ` kbuild test robot
2015-08-26 11:44 [asoc:topic/rockchip 1/4] sound/soc/rockchip/rockchip_max98090.c:225:3-8: No need to set .owner here. The core will do it kbuild test robot
2015-08-26 11:44 ` [PATCH] ASoC: rockchip: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-08-26 11:44 ` 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=20181225043826.GA158508@lkp-ib04.lkp.intel.com \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=katsuhiro@katsuster.net \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.