From: Adrian Bunk <bunk@stusta.de>
To: mhalcrow@us.ibm.com, phillip@hellewell.homeip.net
Cc: ecryptfs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [2.6 patch] make ecryptfs_version_str_map[] static
Date: Mon, 20 Nov 2006 03:24:06 +0100 [thread overview]
Message-ID: <20061120022406.GM31879@stusta.de> (raw)
This patch makes the needlessly global ecryptfs_version_str_map[]
static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.19-rc5-mm2/fs/ecryptfs/main.c.old 2006-11-20 01:27:17.000000000 +0100
+++ linux-2.6.19-rc5-mm2/fs/ecryptfs/main.c 2006-11-20 01:27:25.000000000 +0100
@@ -692,7 +692,7 @@
static struct ecryptfs_attribute sysfs_attr_version = __ATTR_RO(version);
-struct ecryptfs_version_str_map_elem {
+static struct ecryptfs_version_str_map_elem {
u32 flag;
char *str;
} ecryptfs_version_str_map[] = {
next reply other threads:[~2006-11-20 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 2:24 Adrian Bunk [this message]
2006-11-20 16:13 ` [2.6 patch] make ecryptfs_version_str_map[] static Michael Halcrow
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=20061120022406.GM31879@stusta.de \
--to=bunk@stusta.de \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=phillip@hellewell.homeip.net \
/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