linux-kernel - [PATCH -next] proc_fs.h: fix build error when PROC

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]

Message-ID: <517E9A49.5080106@infradead.org>
Date:	Mon, 29 Apr 2013 09:05:29 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled

From: Randy Dunlap <rdunlap@...radead.org>

Fix build error when CONFIG_PROC_FS is not enabled:
(remove duplicated line)

include/linux/proc_fs.h:58:20: error: redefinition of 'proc_set_size'
include/linux/proc_fs.h:51:20: note: previous definition of 'proc_set_size' was here

Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
---
 include/linux/proc_fs.h |    1 -
 1 file changed, 1 deletion(-)

--- linux-next-20130429.orig/include/linux/proc_fs.h
+++ linux-next-20130429/include/linux/proc_fs.h
@@ -55,7 +55,6 @@ static inline void *proc_get_parent_data
 static inline struct proc_dir_entry *proc_create_data(const char *name,
 	umode_t mode, struct proc_dir_entry *parent,
 	const struct file_operations *proc_fops, void *data) { return NULL; }
-static inline void proc_set_size(struct proc_dir_entry *de, loff_t size) {}
 
 static inline void proc_remove(struct proc_dir_entry *de) {}
 static inline void remove_proc_entry(const char *name, struct proc_dir_entry *parent) {}
--
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/