linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: kbuild-all@01.org, Kishon Vijay Abraham I <kishon@ti.com>,
	Igal Liberman <igall@marvell.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] phy: fix platform_no_drv_owner.cocci warnings
Date: Tue, 26 Feb 2019 04:34:28 +0800	[thread overview]
Message-ID: <20190225203427.GA13804@lkp-ne04> (raw)
In-Reply-To: <201902260410.0o0iqLaG%fengguang.wu@intel.com>

From: kbuild test robot <lkp@intel.com>

drivers/phy/marvell/phy-mvebu-a3700-utmi.c:269: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: cc8b7a0ae866 ("phy: add A3700 UTMI PHY driver")
CC: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   2b46440ea71508f7037566dbbab3567d1a64093d
commit: cc8b7a0ae866bb2ac8e4d089173a5e676105c8cb [6049/11177] phy: add A3700 UTMI PHY driver

 phy-mvebu-a3700-utmi.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/phy/marvell/phy-mvebu-a3700-utmi.c
+++ b/drivers/phy/marvell/phy-mvebu-a3700-utmi.c
@@ -266,7 +266,6 @@ static struct platform_driver mvebu_a370
 	.probe	= mvebu_a3700_utmi_phy_probe,
 	.driver	= {
 		.name		= "mvebu-a3700-utmi-phy",
-		.owner		= THIS_MODULE,
 		.of_match_table	= mvebu_a3700_utmi_of_match,
 	 },
 };

           reply	other threads:[~2019-02-25 20:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201902260410.0o0iqLaG%fengguang.wu@intel.com>]

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=20190225203427.GA13804@lkp-ne04 \
    --to=lkp@intel.com \
    --cc=igall@marvell.com \
    --cc=kbuild-all@01.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquel.raynal@bootlin.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).