From: kernel test robot <lkp@intel.com>
To: Marek Vasut <marex@denx.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Robert Foss <robert.foss@linaro.org>
Subject: [PATCH] drm: bridge: icn6211: fix platform_no_drv_owner.cocci warnings
Date: Fri, 1 Apr 2022 19:07:59 +0800 [thread overview]
Message-ID: <YkbdDw8wt/AP+ktu@4f141e9bb993> (raw)
In-Reply-To: <202204011947.10abPzIP-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
drivers/gpu/drm/bridge/chipone-icn6211.c:645: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: 8dde6f7452a1 ("drm: bridge: icn6211: Add I2C configuration support")
CC: Marek Vasut <marex@denx.de>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tree: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
head: 3d7039e1e64980a5eb424373b3a5843b7d7891aa
commit: 8dde6f7452a198a870f74a38118bb1a63da7632e [28/38] drm: bridge: icn6211: Add I2C configuration support
:::::: branch date: 19 hours ago
:::::: commit date: 20 hours ago
drivers/gpu/drm/bridge/chipone-icn6211.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/gpu/drm/bridge/chipone-icn6211.c
+++ b/drivers/gpu/drm/bridge/chipone-icn6211.c
@@ -642,7 +642,6 @@ static struct i2c_driver chipone_i2c_dri
.id_table = chipone_i2c_id,
.driver = {
.name = "chipone-icn6211-i2c",
- .owner = THIS_MODULE,
.of_match_table = chipone_of_match,
},
};
prev parent reply other threads:[~2022-04-01 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 11:12 [drm-misc:drm-misc-next 28/38] drivers/gpu/drm/bridge/chipone-icn6211.c:645:3-8: No need to set .owner here. The core will do it kernel test robot
2022-04-01 11:07 ` kernel test robot [this message]
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=YkbdDw8wt/AP+ktu@4f141e9bb993 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robert.foss@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome