linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lkp@intel.com (kbuild test robot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor_v2: fix platform_no_drv_owner.cocci warnings
Date: Mon, 15 Feb 2016 17:34:20 +0800	[thread overview]
Message-ID: <20160215093420.GA124287@roam> (raw)
In-Reply-To: <1455523083-25506-1-git-send-email-thomas.petazzoni@free-electrons.com>

drivers/dma/mv_xor_v2.c:870: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: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

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

--- a/drivers/dma/mv_xor_v2.c
+++ b/drivers/dma/mv_xor_v2.c
@@ -867,7 +867,6 @@ static struct platform_driver mv_xor_v2_
 	.probe		= mv_xor_v2_probe,
 	.remove		= mv_xor_v2_remove,
 	.driver		= {
-		.owner	= THIS_MODULE,
 		.name	= "mv_xor_v2",
 		.of_match_table = of_match_ptr(mv_xor_v2_dt_ids),
 	},

  parent reply	other threads:[~2016-02-15  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  7:58 [PATCH] dma: mv_xor_v2: new driver Thomas Petazzoni
2016-02-15  9:09 ` kbuild test robot
2016-02-15  9:50   ` Thomas Petazzoni
2016-02-15  9:59     ` Marc Zyngier
2016-02-15 10:58       ` Thomas Petazzoni
2016-02-15  9:34 ` kbuild test robot [this message]
2016-02-15  9:34 ` kbuild test robot
2016-02-15  9:56 ` kbuild test robot
2016-02-22  2:53 ` Rob Herring
2016-02-22  7:21   ` Thomas Petazzoni
2016-02-22 20:02     ` Rob Herring
2016-02-22  3:27 ` Vinod Koul
2016-02-22  9:16   ` Thomas Petazzoni
2016-02-22 19:58     ` Rob Herring
2016-02-23  3:02     ` Vinod Koul
2016-06-15 14:08   ` Thomas Petazzoni
2016-06-15 16:41     ` Vinod Koul
2016-06-16 12:42       ` Thomas Petazzoni
2016-06-17  2:39         ` Vinod Koul

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=20160215093420.GA124287@roam \
    --to=lkp@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).