devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, dmitry.torokhov@gmail.com, fery@cypress.com,
	robh+dt@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	devicetree@vger.kernel.org, mylene.josserand@free-electrons.com,
	thomas.petazzoni@free-electrons.com,
	maxime.ripard@free-electrons.com
Subject: [PATCH] Input: fix platform_no_drv_owner.cocci warnings
Date: Tue, 30 May 2017 01:16:21 +0800	[thread overview]
Message-ID: <20170529171620.GA56706@lkp-hsx03.lkp.intel.com> (raw)
In-Reply-To: <20170529144538.29187-2-mylene.josserand@free-electrons.com>

drivers/input/touchscreen/cyttsp5.c:1162: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: Mylène Josserand <mylene.josserand@free-electrons.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

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

--- a/drivers/input/touchscreen/cyttsp5.c
+++ b/drivers/input/touchscreen/cyttsp5.c
@@ -1159,7 +1159,6 @@ static int cyttsp5_i2c_remove(struct i2c
 static struct i2c_driver cyttsp5_i2c_driver = {
 	.driver = {
 		.name = CYTTSP5_NAME,
-		.owner = THIS_MODULE,
 		.of_match_table = cyttsp5_of_match,
 	},
 	.probe = cyttsp5_i2c_probe,

  parent reply	other threads:[~2017-05-29 17:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 14:45 [PATCH 0/2] Input: Add Cypress Gen5 Touchscreen driver Mylène Josserand
2017-05-29 14:45 ` [PATCH 1/2] Input: Add driver for Cypress Generation 5 touchscreen Mylène Josserand
2017-05-29 17:16   ` kbuild test robot
2017-05-29 17:16   ` kbuild test robot [this message]
2017-05-30  8:02   ` Maxime Ripard
2017-06-06  8:03     ` Mylene Josserand
2017-06-06 12:04       ` Maxime Ripard
2017-06-06 14:32         ` Mylene Josserand
     [not found]           ` <0232a641-c741-1f95-9086-840b31f5d055-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-06-07  9:16             ` Maxime Ripard
2017-05-30  8:11   ` Thomas Petazzoni
     [not found]   ` <20170529144538.29187-2-mylene.josserand-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-05-30  8:43     ` Thomas Petazzoni
     [not found]       ` <20170530104302.6db658f0-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-06-06 13:20         ` Mylene Josserand
2017-05-29 14:45 ` [PATCH 2/2] Documentation: DT: bindings: input: Add documentation for cyttsp5 Mylène Josserand
2017-06-07 20:26   ` Rob Herring
2017-06-07 20:40     ` Dmitry Torokhov
2017-06-09 11:32       ` Mylene Josserand
2017-06-09 11:11     ` Mylene Josserand
  -- strict thread matches above, loose matches on Subject: below --
2017-12-01 15:39 [PATCH v4 1/2] Input: Add driver for Cypress Generation 5 touchscreen Mylène Josserand
2017-12-03 14:29 ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings 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=20170529171620.GA56706@lkp-hsx03.lkp.intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=fery@cypress.com \
    --cc=kbuild-all@01.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mylene.josserand@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@free-electrons.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).