public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Michael A. Halcrow" <mike@halcrow.us>, Serge Hallyn <hallyn@cs.wm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] security/seclvl.c: make some code static
Date: Sun, 28 Nov 2004 19:56:22 +0100	[thread overview]
Message-ID: <20041128185622.GC4390@stusta.de> (raw)

The patch below makes some needlessly global code static.


diffstat output:
 security/seclvl.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.10-rc2-mm3-full/security/seclvl.c.old	2004-11-28 03:32:23.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/security/seclvl.c	2004-11-28 03:34:28.000000000 +0100
@@ -170,7 +170,7 @@
 /**
  * Callback function pointers for show and store
  */
-struct sysfs_ops seclvlfs_sysfs_ops = {
+static struct sysfs_ops seclvlfs_sysfs_ops = {
 	.show = seclvl_attr_show,
 	.store = seclvl_attr_store,
 };
@@ -275,7 +275,7 @@
 }
 
 /* Generate sysfs_attr_seclvl */
-struct seclvl_attribute sysfs_attr_seclvl =
+static struct seclvl_attribute sysfs_attr_seclvl =
 __ATTR(seclvl, (S_IFREG | S_IRUGO | S_IWUSR), seclvl_read_file,
        seclvl_write_file);
 
@@ -386,7 +386,7 @@
 }
 
 /* Generate sysfs_attr_passwd */
-struct seclvl_attribute sysfs_attr_passwd =
+static struct seclvl_attribute sysfs_attr_passwd =
 __ATTR(passwd, (S_IFREG | S_IRUGO | S_IWUSR), seclvl_read_passwd,
        seclvl_write_passwd);
 


             reply	other threads:[~2004-11-28 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 18:56 Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-23 10:16 [2.6 patch] security/seclvl.c: make some code static Adrian Bunk
2005-01-23 22:59 ` Chris Wright

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=20041128185622.GC4390@stusta.de \
    --to=bunk@stusta.de \
    --cc=hallyn@cs.wm.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@halcrow.us \
    /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