From: mark gross <markgross@thegnar.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
mark gross <markgross@thegnar.org>
Subject: Re: linux-next: build warning after merge of the suspend tree
Date: Mon, 23 May 2011 07:18:46 -0700 [thread overview]
Message-ID: <20110523141846.GA8122@gvim.org> (raw)
In-Reply-To: <20110523150636.ccd83777.sfr@canb.auug.org.au>
On Mon, May 23, 2011 at 03:06:36PM +1000, Stephen Rothwell wrote:
> Hi Rafael,
>
> After merging the suspend tree, today's linux-next build (i386 defconfig
> among others) produced this warning:
>
> kernel/pm_qos_params.c: In function 'pm_qos_power_write':
> kernel/pm_qos_params.c:420: warning: passing argument 3 of 'kstrtol' from incompatible pointer type
> include/linux/kernel.h:210: note: expected 'long int *' but argument is of type 's32 *'
>
> Intreoduced by commit 365daa955e03 ("PM: Correct PM QOS's user mode
> interface to work with ascii input per").
Gah! I'm sorry about that.
attached is a fix.
--mark
signed-off-by:markgross <markgross@thegnar.org>
>From a8f0587b9ae598be5ca4c3cdda4e0ced6ca9baaf Mon Sep 17 00:00:00 2001
From: mgross <mgross@cr48>
Date: Mon, 23 May 2011 07:14:09 -0700
Subject: [PATCH] clean up a compile time warning in the use of strict_strtol but that was
passing an s32 * when it should be passing a long *
---
kernel/pm_qos_params.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/pm_qos_params.c b/kernel/pm_qos_params.c
index d61ecf3..dd37c56 100644
--- a/kernel/pm_qos_params.c
+++ b/kernel/pm_qos_params.c
@@ -405,6 +405,7 @@ static ssize_t pm_qos_power_write(struct file *filp, const char __user *buf,
size_t count, loff_t *f_pos)
{
s32 value;
+ long safe_int;
int x;
char ascii_value[11];
struct pm_qos_request_list *pm_qos_req;
@@ -417,10 +418,11 @@ static ssize_t pm_qos_power_write(struct file *filp, const char __user *buf,
ascii_value[count] = 0;
if (copy_from_user(ascii_value, buf, count))
return -EFAULT;
- if ((x=strict_strtol(ascii_value, 16, &value)) != 0){
- pr_debug("%s, 0x%x, 0x%x\n",ascii_value, value, x);
+ if ((x=strict_strtol(ascii_value, 16, &safe_int)) != 0){
+ pr_debug("%s, 0x%lx, 0x%x\n",ascii_value, safe_int, x);
return -EINVAL;
}
+ value = (s32) safe_int;
} else
return -EINVAL;
--
1.7.4.1
next prev parent reply other threads:[~2011-05-23 14:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 5:06 linux-next: build warning after merge of the suspend tree Stephen Rothwell
2011-05-23 14:18 ` mark gross [this message]
2011-05-23 15:24 ` Randy Dunlap
2011-05-23 16:21 ` Milton Miller
2011-05-23 17:42 ` Milton Miller
2011-05-24 6:13 ` mark gross
2011-05-23 18:57 ` Rafael J. Wysocki
2011-05-23 19:54 ` Rafael J. Wysocki
2011-05-24 6:34 ` mark gross
2011-05-24 21:30 ` Rafael J. Wysocki
2011-05-26 1:58 ` mark gross
-- strict thread matches above, loose matches on Subject: below --
2010-02-12 4:57 Stephen Rothwell
2010-02-12 11:32 ` Rafael J. Wysocki
2010-02-12 12:25 ` Stephen Rothwell
2010-02-11 6:10 Stephen Rothwell
2010-02-11 13:11 ` Rafael J. Wysocki
2010-02-11 15:32 ` Alan Stern
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=20110523141846.GA8122@gvim.org \
--to=markgross@thegnar.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).