From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6486] linux-user: fix signal.c warning
Date: Fri, 30 Jan 2009 20:15:33 +0000 [thread overview]
Message-ID: <E1LSzm1-0004fK-H3@cvs.savannah.gnu.org> (raw)
Revision: 6486
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6486
Author: aurel32
Date: 2009-01-30 20:15:32 +0000 (Fri, 30 Jan 2009)
Log Message:
-----------
linux-user: fix signal.c warning
This patch fixes:
linux-user/signal.c:1403: warning: no previous prototype for 'do_sigreturn_v1'
linux-user/signal.c:1473: warning: no previous prototype for 'do_sigreturn_v2'
linux-user/signal.c:1511: warning: no previous prototype for 'do_rt_sigreturn_v1'
linux-user/signal.c:1552: warning: no previous prototype for 'do_rt_sigreturn_v2'
by making the appropriate functions static.
Signed-off-by: Nathan Froyd <froydnj@codesourcery.com>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Modified Paths:
--------------
trunk/linux-user/signal.c
Modified: trunk/linux-user/signal.c
===================================================================
--- trunk/linux-user/signal.c 2009-01-30 20:09:01 UTC (rev 6485)
+++ trunk/linux-user/signal.c 2009-01-30 20:15:32 UTC (rev 6486)
@@ -1399,7 +1399,7 @@
return err;
}
-long do_sigreturn_v1(CPUState *env)
+static long do_sigreturn_v1(CPUState *env)
{
abi_ulong frame_addr;
struct sigframe_v1 *frame;
@@ -1469,7 +1469,7 @@
return 0;
}
-long do_sigreturn_v2(CPUState *env)
+static long do_sigreturn_v2(CPUState *env)
{
abi_ulong frame_addr;
struct sigframe_v2 *frame;
@@ -1507,7 +1507,7 @@
}
}
-long do_rt_sigreturn_v1(CPUState *env)
+static long do_rt_sigreturn_v1(CPUState *env)
{
abi_ulong frame_addr;
struct rt_sigframe_v1 *frame;
@@ -1548,7 +1548,7 @@
return 0;
}
-long do_rt_sigreturn_v2(CPUState *env)
+static long do_rt_sigreturn_v2(CPUState *env)
{
abi_ulong frame_addr;
struct rt_sigframe_v2 *frame;
reply other threads:[~2009-01-30 20:15 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=E1LSzm1-0004fK-H3@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).