linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, wsa@the-dreams.de, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, jiri@resnulli.us,
	Vadim Pasternak <vadimp@mellanox.com>,
	Michael Shych <michaelsh@mellanox.com>
Subject: [PATCH] i2c: mux: mellanox: fix platform_no_drv_owner.cocci warnings
Date: Thu, 25 Aug 2016 14:50:30 +0800	[thread overview]
Message-ID: <20160825065030.GA56099@lkp-sb04.intel.com> (raw)
In-Reply-To: <1472046988-111956-1-git-send-email-vadimp@mellanox.com>

drivers/i2c/muxes/i2c-mux-mlxcpld.c:329: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: Vadim Pasternak <vadimp@mellanox.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 i2c-mux-mlxcpld.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/i2c/muxes/i2c-mux-mlxcpld.c
+++ b/drivers/i2c/muxes/i2c-mux-mlxcpld.c
@@ -326,7 +326,6 @@ static int mlxcpld_mux_remove(struct i2c
 static struct i2c_driver mlxcpld_mux_driver = {
 	.driver		= {
 		.name	= "mlxcpld-mux",
-		.owner	= THIS_MODULE,
 	},
 	.probe		= mlxcpld_mux_probe,
 	.remove		= mlxcpld_mux_remove,

      parent reply	other threads:[~2016-08-25  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  6:50 [patch 2/2] i2c: mux: mellanox: add driver kbuild test robot
2016-08-24 13:56 ` vadimp
2016-08-24 13:54   ` Peter Rosin
2016-08-24 16:20     ` Vadim Pasternak
2016-08-25  8:53       ` Peter Rosin
2016-08-25 10:08         ` Vadim Pasternak
2016-08-25  6:50   ` kbuild test robot [this message]

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=20160825065030.GA56099@lkp-sb04.intel.com \
    --to=lkp@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kbuild-all@01.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelsh@mellanox.com \
    --cc=vadimp@mellanox.com \
    --cc=wsa@the-dreams.de \
    /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).