linux-kernel - [PATCH 17/21] fs: Mark function as static in proc/array.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 9 Feb 2014 18:48:44 +0530
From:	Rashika Kheria <rashika.kheria@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Sameer Nanda <snanda@...omium.org>,
	Rashika Kheria <rashika.kheria@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Mel Gorman <mgorman@...e.de>, josh@...htriplett.org
Subject: [PATCH 17/21] fs: Mark function as static in proc/array.c

Mark function as static in proc/array.c because it is not used outside
this file.

This eliminates the following warning in proc/array.c:
fs/proc/array.c:712:5: warning: no previous prototype for ‘children_seq_release’ [-Wmissing-prototypes]

Signed-off-by: Rashika Kheria <rashika.kheria@...il.com>
Reviewed-by: Josh Triplett <josh@...htriplett.org>
---
 fs/proc/array.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/proc/array.c b/fs/proc/array.c
index 656e401..2265b11 100644
--- a/fs/proc/array.c
+++ b/fs/proc/array.c
@@ -699,7 +699,7 @@ static int children_seq_open(struct inode *inode, struct file *file)
 	return ret;
 }
 
-int children_seq_release(struct inode *inode, struct file *file)
+static int children_seq_release(struct inode *inode, struct file *file)
 {
 	seq_release(inode, file);
 	return 0;
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/