From: Fengguang Wu <fengguang.wu@intel.com>
To: linux-pm@vger.kernel.org
Cc: Lan Tianyu <tianyu.lan@intel.com>,
Zhang Rui <rui.zhang@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Thermal: fix platform_no_drv_owner.cocci warnings
Date: Mon, 17 Nov 2014 14:24:36 +0800 [thread overview]
Message-ID: <20141117062436.GA26230@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <201411161721.jEzvtBAi%fengguang.wu@intel.com>
drivers/thermal/int340x_thermal/int3403_thermal.c:468: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
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
int3403_thermal.c | 1 -
1 file changed, 1 deletion(-)
--- a/drivers/thermal/int340x_thermal/int3403_thermal.c
+++ b/drivers/thermal/int340x_thermal/int3403_thermal.c
@@ -465,7 +465,6 @@ static struct platform_driver int3403_dr
.remove = int3403_remove,
.driver = {
.name = "int3403 thermal",
- .owner = THIS_MODULE,
.acpi_match_table = int3403_device_ids,
},
};
next parent reply other threads:[~2014-11-17 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201411161721.jEzvtBAi%fengguang.wu@intel.com>
2014-11-17 6:24 ` Fengguang Wu [this message]
2014-11-17 7:57 ` [PATCH] Thermal: fix platform_no_drv_owner.cocci warnings Zhang Rui
[not found] <201412212210.5BfVGAAA%fengguang.wu@intel.com>
2014-12-21 14:21 ` kbuild test robot
2014-12-22 1:54 ` Aaron Lu
2017-06-06 7:50 [PATCH 2/2] thermal: add brcmstb AVS TMON driver kbuild test robot
2017-06-05 21:09 ` Markus Mayer
2017-06-06 7:50 ` [PATCH] thermal: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-06-06 7:50 ` kbuild test robot
2017-06-06 7:50 ` kbuild test robot
2019-04-23 19:32 [soc-thermal:for-kernelci 34/35] drivers/thermal/thermal_mmio.c:120:3-8: No need to set .owner here. The core will do it kbuild test robot
2019-04-23 19:32 ` [PATCH] thermal: fix platform_no_drv_owner.cocci warnings kbuild test robot
2019-04-28 11:24 ` Shenhar, Talel
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=20141117062436.GA26230@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=tianyu.lan@intel.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 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.