Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: mfelton1@nuvoton.com, Anatol Pomozov <anatol.pomozov@gmail.com>,
	alsa-devel@alsa-project.org, benzh@google.com,
	broonie@kernel.org, kbuild-all@01.org, ccchang12@nuvoton.com
Subject: [PATCH] ASoC: nau8825: fix platform_no_drv_owner.cocci warnings
Date: Sat, 3 Oct 2015 03:37:59 +0800	[thread overview]
Message-ID: <20151002193759.GA166239@athens> (raw)
In-Reply-To: <1443804554-36592-1-git-send-email-anatol.pomozov@gmail.com>

sound/soc/codecs/nau8825.c:1096: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: Anatol Pomozov <anatol.pomozov@gmail.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 nau8825.c |    1 -
 1 file changed, 1 deletion(-)

--- a/sound/soc/codecs/nau8825.c
+++ b/sound/soc/codecs/nau8825.c
@@ -1093,7 +1093,6 @@ MODULE_DEVICE_TABLE(of, nau8825_of_ids);
 static struct i2c_driver nau8825_driver = {
 	.driver = {
 		.name = "nau8825",
-		.owner = THIS_MODULE,
 		.of_match_table = of_match_ptr(nau8825_of_ids),
 	},
 	.probe = nau8825_i2c_probe,

  parent reply	other threads:[~2015-10-02 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 19:37 [PATCH] ASoC: nau8825: Add driver for headset chip Nuvoton 8825 kbuild test robot
2015-10-02 16:49 ` Anatol Pomozov
2015-10-02 16:55   ` Anatol Pomozov
2015-10-02 19:37   ` kbuild test robot [this message]
2015-10-07 10:38     ` Applied "ASoC: nau8825: fix platform_no_drv_owner.cocci warnings" to the asoc tree Mark Brown
2015-10-07 10:38   ` Applied "ASoC: nau8825: Add driver for headset chip Nuvoton 8825" " 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=20151002193759.GA166239@athens \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=anatol.pomozov@gmail.com \
    --cc=benzh@google.com \
    --cc=broonie@kernel.org \
    --cc=ccchang12@nuvoton.com \
    --cc=kbuild-all@01.org \
    --cc=mfelton1@nuvoton.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