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: fix platform_no_drv_owner.cocci warnings
Date: Tue, 23 Aug 2016 20:18:04 +0800	[thread overview]
Message-ID: <20160823121804.GA80500@lkp-sb04> (raw)
In-Reply-To: <1471502328-28305-2-git-send-email-yao.yuan@freescale.com>

drivers/dma/qoriq-qdma.c:879: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: Yuan Yao <yao.yuan@nxp.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---

 qoriq-qdma.c |    1 -
 1 file changed, 1 deletion(-)

--- a/drivers/dma/qoriq-qdma.c
+++ b/drivers/dma/qoriq-qdma.c
@@ -876,7 +876,6 @@ MODULE_DEVICE_TABLE(of, fsl_qdma_dt_ids)
 static struct platform_driver fsl_qdma_driver = {
 	.driver		= {
 		.name	= "fsl-qdma",
-		.owner  = THIS_MODULE,
 		.of_match_table = fsl_qdma_dt_ids,
 	},
 	.probe          = fsl_qdma_probe,

  parent reply	other threads:[~2016-08-23 12:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  6:38 [PATCH v1 0/5] dma: Add QorIQ qDMA engine driver support Yuan Yao
2016-08-18  6:38 ` [PATCH v1 1/5] " Yuan Yao
2016-08-18  9:16   ` Russell King - ARM Linux
2016-08-24  3:39     ` Yao Yuan
2016-08-23 12:18   ` kbuild test robot
2016-08-23 12:18   ` kbuild test robot [this message]
2016-08-18  6:38 ` [PATCH v1 2/5] dma: Add device tree binding for QorIQ qDMA driver Yuan Yao
2016-08-18  6:38 ` [PATCH v1 3/5] MAINTAINERS: add maintainer entry for QorIQ QDMA driver Yuan Yao
2016-08-18  6:38 ` [PATCH v1 4/5] ARM: dts: ls1043a: add qDMA node Yuan Yao
2016-08-29  7:29   ` Alexander Stein
2016-08-29  7:34   ` Alexander Stein
2016-08-31  4:17     ` Yao Yuan
2016-08-18  6:38 ` [PATCH v1 5/5] ARM: dts: ls1021a: " Yuan Yao

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=20160823121804.GA80500@lkp-sb04 \
    --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).