From: Alan Cox <alan@linux.intel.com>
To: jmorris@namei.org, linux-kernel@vger.kernel.org
Subject: [PATCH] selinux: Fix warnings
Date: Wed, 18 Nov 2009 14:39:51 +0000 [thread overview]
Message-ID: <20091118143951.4691.33970.stgit@localhost.localdomain> (raw)
scripts/selinux/genheaders/genheaders.c:20: warning: no previous prototype
for ‘usage’
scripts/selinux/genheaders/genheaders.c:26: warning: no previous prototype
for ‘stoupperx’
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
| 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--git a/scripts/selinux/genheaders/genheaders.c b/scripts/selinux/genheaders/genheaders.c
index 3b16145..771b86f 100644
--- a/scripts/selinux/genheaders/genheaders.c
+++ b/scripts/selinux/genheaders/genheaders.c
@@ -17,13 +17,13 @@ struct security_class_mapping {
const char *progname;
-void usage(void)
+static void usage(void)
{
printf("usage: %s flask.h av_permissions.h\n", progname);
exit(1);
}
-char *stoupperx(const char *s)
+static char *stoupperx(const char *s)
{
char *s2 = strdup(s);
char *p;
next reply other threads:[~2009-11-18 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:39 Alan Cox [this message]
2009-11-18 16:04 ` [PATCH] selinux: Fix warnings Américo Wang
2009-11-18 22:09 ` James Morris
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=20091118143951.4691.33970.stgit@localhost.localdomain \
--to=alan@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.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