From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [PATCH] ZEN: fix platform_no_drv_owner.cocci warnings
Date: Thu, 02 Apr 2020 04:13:31 +0800 [thread overview]
Message-ID: <20200401201308.GA23173@85fc00d466e9> (raw)
In-Reply-To: <202004020459.5iANHknE%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
From: kbuild test robot <lkp@intel.com>
drivers/scsi/vhba/vhba.c:1045:9-14: 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: 571a78afe655 ("ZEN: Add VHBA driver")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
tree: https://github.com/zen-kernel/zen-kernel 5.6/zen-sauce
head: d33eeeb62ca70eeba3234089e7bc61ac11e8d351
commit: 571a78afe655a6e606ff127b57f7a01d3bc68614 [2/22] ZEN: Add VHBA driver
vhba.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/scsi/vhba/vhba.c
+++ b/drivers/scsi/vhba/vhba.c
@@ -1042,7 +1042,6 @@ static struct platform_device vhba_platf
static struct platform_driver vhba_platform_driver = {
.driver = {
- .owner = THIS_MODULE,
.name = "vhba",
},
.probe = vhba_probe,
next prev parent reply other threads:[~2020-04-01 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 20:13 [zen-kernel-zen-kernel:5.6/zen-sauce 2/22] drivers/scsi/vhba/vhba.c:1045:9-14: No need to set .owner here. The core will do it kbuild test robot
2020-04-01 20:13 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-26 11:01 [PATCH] ZEN: fix platform_no_drv_owner.cocci warnings Julia Lawall
2020-07-26 6:29 [zen-kernel-zen-kernel:5.7/zen-sauce 2/22] drivers/scsi/vhba/vhba.c:181:8-27: atomic_dec_and_test variation before object free at line 182 kernel test robot
2020-07-26 6:29 ` [PATCH] ZEN: fix platform_no_drv_owner.cocci warnings kernel test robot
2019-04-14 5:50 Julia Lawall
2019-04-15 6:31 ` Reshetova, Elena
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=20200401201308.GA23173@85fc00d466e9 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.