All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: kbuild-all@01.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>
Subject: [PATCH] pinctrl: renesas: fix platform_no_drv_owner.cocci warnings
Date: Thu, 11 Oct 2018 00:02:55 +0800	[thread overview]
Message-ID: <20181010160255.GA17268@ivb43> (raw)
In-Reply-To: <201810110049.r0RJkFTF%fengguang.wu@intel.com>

From: kbuild test robot <fengguang.wu@intel.com>

drivers/pinctrl/pinctrl-rzn1.c:935: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

Fixes: 4e53b5004745 ("pinctrl: renesas: Renesas RZ/N1 pinctrl driver")
CC: Phil Edworthy <phil.edworthy@renesas.com>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git sh-pfc-for-v4.20
head:   ef26d96023a4c34b1bcc4294f570df2b63a1b952
commit: 4e53b5004745ef26a37bca4933b2d3ea71313f2a [24/25] pinctrl: renesas: Renesas RZ/N1 pinctrl driver

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

--- a/drivers/pinctrl/pinctrl-rzn1.c
+++ b/drivers/pinctrl/pinctrl-rzn1.c
@@ -932,7 +932,6 @@ static struct platform_driver rzn1_pinct
 	.remove = rzn1_pinctrl_remove,
 	.driver	= {
 		.name		= "rzn1-pinctrl",
-		.owner		= THIS_MODULE,
 		.of_match_table	= rzn1_pinctrl_match,
 	},
 };

  reply	other threads:[~2018-10-10 23:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 16:02 [renesas-drivers:sh-pfc-for-v4.20 24/25] drivers/pinctrl/pinctrl-rzn1.c:935:3-8: No need to set .owner here. The core will do it kbuild test robot
2018-10-10 16:02 ` kbuild test robot [this message]
2018-10-11  9:39   ` [PATCH] pinctrl: renesas: fix platform_no_drv_owner.cocci warnings Phil Edworthy

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=20181010160255.GA17268@ivb43 \
    --to=fengguang.wu@intel.com \
    --cc=geert+renesas@glider.be \
    --cc=jacopo+renesas@jmondi.org \
    --cc=kbuild-all@01.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=phil.edworthy@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.