From: Bhumika Goyal <bhumirks@gmail.com>
To: julia.lawall@lip6.fr, peter@piie.net, dvhart@infradead.org,
andy@infradead.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, sujith.thomas@intel.com
Cc: Bhumika Goyal <bhumirks@gmail.com>
Subject: [PATCH 1/2] acerhdf: add const to thermal_cooling_device_ops structure
Date: Wed, 21 Jun 2017 12:34:16 +0530 [thread overview]
Message-ID: <1498028657-12059-2-git-send-email-bhumirks@gmail.com> (raw)
In-Reply-To: <1498028657-12059-1-git-send-email-bhumirks@gmail.com>
Declare thermal_cooling_device_ops structure as const as it is only passed
as an argument to the function thermal_cooling_device_register and this
argument is of type const. So, declare the structure as const.
Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
---
drivers/platform/x86/acerhdf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/x86/acerhdf.c b/drivers/platform/x86/acerhdf.c
index 2acdb0d..ea22591 100644
--- a/drivers/platform/x86/acerhdf.c
+++ b/drivers/platform/x86/acerhdf.c
@@ -557,7 +557,7 @@ static int acerhdf_set_cur_state(struct thermal_cooling_device *cdev,
}
/* bind fan callbacks to fan device */
-static struct thermal_cooling_device_ops acerhdf_cooling_ops = {
+static const struct thermal_cooling_device_ops acerhdf_cooling_ops = {
.get_max_state = acerhdf_get_max_state,
.get_cur_state = acerhdf_get_cur_state,
.set_cur_state = acerhdf_set_cur_state,
--
2.7.4
next prev parent reply other threads:[~2017-06-21 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 7:04 [PATCH 0/2] platform/x86: add const to thermal_cooling_device_ops structures Bhumika Goyal
2017-06-21 7:04 ` Bhumika Goyal [this message]
2017-06-21 7:04 ` [PATCH 2/2] intel_menlow: add const to thermal_cooling_device_ops structure Bhumika Goyal
2017-06-21 21:14 ` [PATCH 0/2] platform/x86: add const to thermal_cooling_device_ops structures Darren Hart
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=1498028657-12059-2-git-send-email-bhumirks@gmail.com \
--to=bhumirks@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@piie.net \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sujith.thomas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox