From: kbuild test robot <lkp@intel.com>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org,
Purna Chandra Mandal <purna.mandal@microchip.com>,
Mark Brown <broonie@kernel.org>,
Joshua Henderson <digitalpeer@digitalpeer.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: [PATCH] spi: spi-pic32: fix platform_no_drv_owner.cocci warnings
Date: Fri, 4 Mar 2016 23:22:38 +0800 [thread overview]
Message-ID: <20160304152238.GA27359@lkp-ib03> (raw)
In-Reply-To: <1457099082-12587-2-git-send-email-purna.mandal@microchip.com>
drivers/spi/spi-pic32.c:993: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: Purna Chandra Mandal <purna.mandal@microchip.com>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
spi-pic32.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/spi/spi-pic32.c
+++ b/drivers/spi/spi-pic32.c
@@ -990,7 +990,6 @@ MODULE_DEVICE_TABLE(of, pic32_spi_of_mat
static struct platform_driver pic32_spi_driver = {
.driver = {
.name = "spi-pic32",
- .owner = THIS_MODULE,
.of_match_table = of_match_ptr(pic32_spi_of_match),
},
.probe = pic32_spi_probe,
next prev parent reply other threads:[~2016-03-04 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 13:44 [PATCH v2 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal
2016-03-04 13:44 ` [PATCH v2 2/2] spi: spi-pic32: Add PIC32 SPI master driver Purna Chandra Mandal
2016-03-04 15:22 ` kbuild test robot
2016-03-04 15:22 ` kbuild test robot [this message]
2016-03-05 3:40 ` Mark Brown
2016-03-05 15:15 ` Purna Chandra Mandal
2016-03-06 2:25 ` Mark Brown
2016-03-05 6:36 ` kbuild test robot
2016-03-05 4:31 ` [PATCH v2 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Rob Herring
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=20160304152238.GA27359@lkp-ib03 \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=digitalpeer@digitalpeer.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=purna.mandal@microchip.com \
--cc=sergei.shtylyov@cogentembedded.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®