From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Alan Cox <alan@linux.intel.com>
Cc: jmorris@namei.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selinux: Fix warnings
Date: Thu, 19 Nov 2009 00:04:59 +0800 [thread overview]
Message-ID: <20091118160459.GA3287@hack> (raw)
In-Reply-To: <20091118143951.4691.33970.stgit@localhost.localdomain>
On Wed, Nov 18, 2009 at 02:39:51PM +0000, Alan Cox wrote:
>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>
Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
>---
>
> scripts/selinux/genheaders/genheaders.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
>diff --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;
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
--
Live like a child, think like the god.
next prev parent reply other threads:[~2009-11-18 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:39 [PATCH] selinux: Fix warnings Alan Cox
2009-11-18 16:04 ` Américo Wang [this message]
2009-11-18 22:09 ` James Morris
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=20091118160459.GA3287@hack \
--to=xiyou.wangcong@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.