public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] pinctrl: fix platform_no_drv_owner.cocci warnings
Date: Tue, 9 Dec 2014 18:12:46 +0800	[thread overview]
Message-ID: <20141209101246.GA23340@waimea> (raw)
In-Reply-To: <201412091835.Agnyz4iN%fengguang.wu@intel.com>

drivers/pinctrl/intel/pinctrl-cherryview.c:1500: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: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 pinctrl-cherryview.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/pinctrl/intel/pinctrl-cherryview.c
+++ b/drivers/pinctrl/intel/pinctrl-cherryview.c
@@ -1497,7 +1497,6 @@ static struct platform_driver chv_pinctr
 	.remove = chv_pinctrl_remove,
 	.driver = {
 		.name = "cherryview-pinctrl",
-		.owner = THIS_MODULE,
 		.acpi_match_table = chv_pinctrl_acpi_match,
 	},
 };

       reply	other threads:[~2014-12-09 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201412091835.Agnyz4iN%fengguang.wu@intel.com>
2014-12-09 10:12 ` kbuild test robot [this message]
     [not found] <201412091859.PtLW5zZR%fengguang.wu@intel.com>
2014-12-09 10:08 ` [PATCH] pinctrl: 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=20141209101246.GA23340@waimea \
    --to=fengguang.wu@intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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