mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Rishiraj Manwatkar <manwatkar@outlook.com>
Cc: kbuild-all@01.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Vandana BN" <bnvandana@gmail.com>,
	"Matt Sickler" <Matt.Sickler@daktronics.com>,
	"Simon Sandström" <simon@nikanor.nu>,
	"Valerio Genovese" <valerio.click@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: kpc2000: Fix: fix platform_no_drv_owner.cocci warnings
Date: Sat, 22 Jun 2019 03:04:08 +0800	[thread overview]
Message-ID: <20190621190408.GA17920@lkp-kbuild07> (raw)
In-Reply-To: <201906220357.jo7Q9YJT%lkp@intel.com>

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

drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c:200: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: abddd78ef465 ("staging: kpc2000: Fix: 'kpc_dma_del_device' and other symbols were not declared")
CC: Rishiraj Manwatkar <manwatkar@outlook.com>
Signed-off-by: kbuild test robot <lkp@intel.com>
---

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   e2d28c40292bdc35553d599e5bbbeaefbab49416
commit: abddd78ef465b86fc89a3d9750bb76a138bc0859 [5641/8196] staging: kpc2000: Fix: 'kpc_dma_del_device' and other symbols were not declared

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

--- a/drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c
+++ b/drivers/staging/kpc2000/kpc_dma/kpc_dma_driver.c
@@ -197,7 +197,6 @@ static struct platform_driver kpc_dma_pl
 	.remove       = kpc_dma_remove,
 	.driver = {
 		.name   = KP_DRIVER_NAME_DMA_CONTROLLER,
-		.owner  = THIS_MODULE,
 	},
 };
 

       reply	other threads:[~2019-06-21 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201906220357.jo7Q9YJT%lkp@intel.com>
2019-06-21 19:04 ` kbuild test robot [this message]
2019-06-22  5:34   ` Greg Kroah-Hartman

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=20190621190408.GA17920@lkp-kbuild07 \
    --to=lkp@intel.com \
    --cc=Matt.Sickler@daktronics.com \
    --cc=bnvandana@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manwatkar@outlook.com \
    --cc=simon@nikanor.nu \
    --cc=valerio.click@gmail.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

all inboxes | Powered by JetHome®