From: kbuild test robot <lkp@intel.com>
To: Ryan Lee <RyanS.Lee@maximintegrated.com>
Cc: kbuild-all@01.org, lgirdwood@gmail.com, broonie@kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com, perex@perex.cz,
tiwai@suse.com, arnd@arndb.de, michael@amarulasolutions.com,
oder_chiou@realtek.com, yesanishhere@gmail.com,
jacob@teenage.engineering, Damien.Horsley@imgtec.com,
bardliao@realtek.com, kuninori.morimoto.gx@renesas.com,
petr@barix.com, lars@metafoo.de, nh6z@nh6z.net,
ryans.lee@maximintegrated.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fix platform_no_drv_owner.cocci warnings
Date: Thu, 24 Nov 2016 02:13:44 +0800 [thread overview]
Message-ID: <20161123181344.GA24123@lkp-wsm-ep2> (raw)
In-Reply-To: <1479877026-5172-1-git-send-email-RyanS.Lee@maximintegrated.com>
sound/soc/codecs/max98927.c:941: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: Ryan Lee <RyanS.Lee@maximintegrated.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
max98927.c | 1 -
1 file changed, 1 deletion(-)
--- a/sound/soc/codecs/max98927.c
+++ b/sound/soc/codecs/max98927.c
@@ -938,7 +938,6 @@ MODULE_DEVICE_TABLE(of, max98927_of_matc
static struct i2c_driver max98927_i2c_driver = {
.driver = {
.name = "max98927",
- .owner = THIS_MODULE,
.of_match_table = of_match_ptr(max98927_of_match),
.pm = NULL,
},
next prev parent reply other threads:[~2016-11-23 18:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 18:13 [PATCH] ALSA SoC MAX98927 driver - Initial release kbuild test robot
2016-11-23 4:57 ` Ryan Lee
2016-11-23 15:46 ` Mark Brown
2016-11-23 17:51 ` kbuild test robot
2016-11-23 18:13 ` kbuild test robot [this message]
2016-11-23 18:56 ` kbuild test robot
2016-11-23 19:20 ` Michael Trimarchi
2016-11-25 5:02 ` [PATCH v2] ALSA SoC MAX98927 driver - Revision Ryan Lee
2016-11-30 18:15 ` Mark Brown
2016-11-28 22:01 ` [PATCH] ALSA SoC MAX98927 driver - Initial release Rob Herring
[not found] <201906240241.S3kwAGar%lkp@intel.com>
2019-06-23 18:50 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2017-02-20 12:05 [PATCH 1/2] add driver for cypress cy8cmbr3102 kbuild test robot
2017-02-20 10:33 ` Patrick Vogelaar
2017-02-20 12:05 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-07-27 14:41 Julia Lawall
2016-08-08 5:47 ` Vinod Koul
2016-02-15 7:34 [media 7/7] PCI bridge driver for PT3 & PXQ3PE kbuild test robot
2016-02-15 6:08 ` info
2016-02-15 7:34 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:44 [PATCH v2 5/6] Add Advantech iManager Backlight driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:44 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:34 [PATCH v2 4/6] Add Advantech iManager I2C driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:34 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:25 [PATCH v2 3/6] Add Advantech iManager HWmon driver kbuild test robot
2016-01-10 9:11 ` richard.dorsch
2016-01-10 10:25 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-10 10:11 [PATCH v2 1/6] Add Advantech iManager MFD core driver kbuild test robot
2016-01-10 9:10 ` richard.dorsch
2016-01-10 10:11 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-09 2:02 [PATCH 6/6] Add Advantech iManager Watchdog driver kbuild test robot
2016-01-08 22:29 ` richard.dorsch
2016-01-09 2:02 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-01-09 0:50 [PATCH 2/6] Add Advantech iManager GPIO driver kbuild test robot
2016-01-08 22:29 ` richard.dorsch
2016-01-09 0:50 ` [PATCH] fix platform_no_drv_owner.cocci warnings kbuild test robot
[not found] <201503291519.K9Z6Qptb%fengguang.wu@intel.com>
2015-03-29 7:49 ` kbuild test robot
2015-03-30 13:05 ` Thierry Reding
2015-04-07 13:09 ` Linus Walleij
2015-04-08 1:24 ` Fengguang Wu
[not found] <201503291545.My1tADgz%fengguang.wu@intel.com>
2015-03-29 7:42 ` kbuild test robot
2015-03-29 16:27 ` Mark Brown
[not found] <201503291531.GP28FwKy%fengguang.wu@intel.com>
2015-03-29 7:33 ` kbuild test robot
2015-03-29 16:24 ` Mark Brown
2015-03-30 12:52 ` Thierry Reding
[not found] <201502131224.TGzEj1Ve%fengguang.wu@intel.com>
2015-02-13 4:49 ` kbuild test robot
[not found] <201501160912.S502Nlmz%fengguang.wu@intel.com>
2015-01-16 1:06 ` kbuild test robot
2015-03-11 11:05 ` Thierry Reding
2015-03-18 1:38 ` Linus Walleij
2015-03-24 10:43 ` Thierry Reding
2015-03-25 1:56 ` Fengguang Wu
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=20161123181344.GA24123@lkp-wsm-ep2 \
--to=lkp@intel.com \
--cc=Damien.Horsley@imgtec.com \
--cc=RyanS.Lee@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacob@teenage.engineering \
--cc=kbuild-all@01.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael@amarulasolutions.com \
--cc=nh6z@nh6z.net \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=petr@barix.com \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=yesanishhere@gmail.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