linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Duggan <aduggan@synaptics.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Christopher Heiny <cheiny@synaptics.com>,
	Stephen Chandler Paul <cpaul@redhat.com>,
	Vincent Huang <vincent.huang@tw.synaptics.com>,
	Chris Healy <cphealy@gmail.com>,
	Andrey Gusakov <andrey.gusakov@cogentembedded.com>
Subject: [PATCH] Input: synaptics-rmi4: fix platform_no_drv_owner.cocci warnings
Date: Wed, 10 Feb 2016 10:45:25 +0800	[thread overview]
Message-ID: <20160210024525.GA34639@lkp-nex05> (raw)
In-Reply-To: <1455068440-11964-1-git-send-email-aduggan@synaptics.com>

drivers/input/rmi4/rmi_i2c.c:373: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: Andrew Duggan <aduggan@synaptics.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

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

--- a/drivers/input/rmi4/rmi_i2c.c
+++ b/drivers/input/rmi4/rmi_i2c.c
@@ -370,7 +370,6 @@ MODULE_DEVICE_TABLE(i2c, rmi_id);
 
 static struct i2c_driver rmi_i2c_driver = {
 	.driver = {
-		.owner	= THIS_MODULE,
 		.name	= "rmi4_i2c",
 		.pm	= &rmi_i2c_pm,
 	},

      reply	other threads:[~2016-02-10  2:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  2:45 [PATCH v4 02/10] Input: synaptics-rmi4: Add I2C transport driver kbuild test robot
2016-02-10  1:40 ` Andrew Duggan
2016-02-10  2:45   ` 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=20160210024525.GA34639@lkp-nex05 \
    --to=lkp@intel.com \
    --cc=aduggan@synaptics.com \
    --cc=andrey.gusakov@cogentembedded.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cheiny@synaptics.com \
    --cc=cpaul@redhat.com \
    --cc=cphealy@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.huang@tw.synaptics.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;
as well as URLs for NNTP newsgroup(s).