From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: [patch] kernel/hrtimer.c sparse warning fix
Date: Mon, 16 Jan 2006 10:59:41 +0100 [thread overview]
Message-ID: <20060116095941.GA25736@elte.hu> (raw)
fix the following Sparse warning:
kernel/hrtimer.c:665:34: warning: incorrect type in argument 2 (different address spaces)
kernel/hrtimer.c:665:34: expected void const *from
kernel/hrtimer.c:665:34: got struct timespec [noderef] *<noident><asn:1>
kernel/hrtimer.c:664:2: warning: dereference of noderef expression
Signed-off-by: Ingo Molnar <mingo@elte.hu>
----
kernel/hrtimer.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
Index: linux/kernel/hrtimer.c
===================================================================
--- linux.orig/kernel/hrtimer.c
+++ linux/kernel/hrtimer.c
@@ -644,7 +644,8 @@ schedule_hrtimer_interruptible(struct hr
static long __sched
nanosleep_restart(struct restart_block *restart, clockid_t clockid)
{
- struct timespec __user *rmtp, tu;
+ struct timespec __user *rmtp;
+ struct timespec tu;
void *rfn_save = restart->fn;
struct hrtimer timer;
ktime_t rem;
reply other threads:[~2006-01-16 9:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060116095941.GA25736@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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