From: kernel test robot <lkp@intel.com>
To: Yusuf Khan <yusisamerican@gmail.com>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, jasowang@redhat.com,
mikelley@microsoft.com, mst@redhat.com,
gregkh@linuxfoundation.org, javier@javigon.com, arnd@arndb.de,
will@kernel.org, axboe@kernel.dk,
Yusuf Khan <yusisamerican@gmail.com>,
Christoph Grenz <christophg+lkml@grenz-bonn.de>
Subject: [PATCH] drivers: ddcci: fix platform_no_drv_owner.cocci warnings
Date: Mon, 4 Apr 2022 21:11:30 +0800 [thread overview]
Message-ID: <YkrugvQSZY0CDZlK@998e223f1083> (raw)
In-Reply-To: <20220403230850.2986-2-yusisamerican@gmail.com>
From: kernel test robot <lkp@intel.com>
drivers/char/ddcci.c:1721: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: Yusuf Khan <yusisamerican@gmail.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
url: https://github.com/intel-lab-lkp/linux/commits/Yusuf-Khan/drivers-ddcci-add-drivers-for-DDCCI/20220404-080905
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git 37fd83916da2e4cae03d350015c82a67b1b334c4
:::::: branch date: 13 hours ago
:::::: commit date: 13 hours ago
drivers/char/ddcci.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/char/ddcci.c
+++ b/drivers/char/ddcci.c
@@ -1718,7 +1718,6 @@ MODULE_DEVICE_TABLE(i2c, ddcci_idtable);
static struct i2c_driver ddcci_driver = {
.driver = {
.name = "ddcci",
- .owner = THIS_MODULE,
},
.id_table = ddcci_idtable,
next prev parent reply other threads:[~2022-04-04 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 23:08 [PATCH v10 0/3] drivers: ddcci: add drivers for DDCCI Yusuf Khan
2022-04-03 23:08 ` [PATCH v10 1/3] " Yusuf Khan
2022-04-04 4:58 ` Greg KH
2022-04-04 13:11 ` kernel test robot [this message]
2022-04-04 13:14 ` kernel test robot
2022-04-03 23:08 ` [PATCH v10 2/3] " Yusuf Khan
2022-04-03 23:08 ` [PATCH v10 3/3] " Yusuf Khan
2022-04-03 23:34 ` [PATCH v10 0/3] " Randy Dunlap
2022-04-04 4:57 ` Greg KH
2022-04-04 11:10 ` Hans de Goede
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=YkrugvQSZY0CDZlK@998e223f1083 \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=christophg+lkml@grenz-bonn.de \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=javier@javigon.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mst@redhat.com \
--cc=will@kernel.org \
--cc=yusisamerican@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®