From: kbuild test robot <fengguang.wu@intel.com>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Avi Fishman <avifishman70@gmail.com>,
Patrick Venture <venture@google.com>,
Nancy Yuen <yuenn@google.com>,
Brendan Higgins <brendanhiggins@google.com>,
openbmc@lists.ozlabs.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] spi: npcm: fix platform_no_drv_owner.cocci warnings
Date: Thu, 15 Nov 2018 15:11:13 +0800 [thread overview]
Message-ID: <20181115071113.GA99225@ivb43> (raw)
In-Reply-To: <201811151510.lC0S0JPS%fengguang.wu@intel.com>
From: kbuild test robot <fengguang.wu@intel.com>
drivers/spi/spi-npcm-pspi.c:470: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: 2a22f1b30cee ("spi: npcm: add NPCM PSPI controller driver")
CC: Tomer Maimon <tmaimon77@gmail.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: f4ad10924cb922842beafe644dd1b2aa8fa55189
commit: 2a22f1b30cee8d1e104a6c5062a609bedbfd5c39 [2986/3290] spi: npcm: add NPCM PSPI controller driver
spi-npcm-pspi.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/spi/spi-npcm-pspi.c
+++ b/drivers/spi/spi-npcm-pspi.c
@@ -467,7 +467,6 @@ static struct platform_driver npcm_pspi_
.driver = {
.name = DRIVER_NAME,
.of_match_table = npcm_pspi_match,
- .owner = THIS_MODULE,
},
.probe = npcm_pspi_probe,
.remove = npcm_pspi_remove,
parent reply other threads:[~2018-11-15 7:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201811151510.lC0S0JPS%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=20181115071113.GA99225@ivb43 \
--to=fengguang.wu@intel.com \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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).