From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled
Date: Mon, 29 Apr 2013 09:05:29 -0700 [thread overview]
Message-ID: <517E9A49.5080106@infradead.org> (raw)
In-Reply-To: <20130429191754.8ee71fb814790bf345516ab8@canb.auug.org.au>
From: Randy Dunlap <rdunlap@infradead.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@infradead.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) {}
next prev parent reply other threads:[~2013-04-29 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 9:17 linux-next: Tree for Apr 29 Stephen Rothwell
2013-04-29 9:17 ` Stephen Rothwell
2013-04-29 15:52 ` linux-next: Tree for Apr 29 (kvm) Randy Dunlap
2013-04-29 16:31 ` Gleb Natapov
2013-04-29 16:46 ` Paolo Bonzini
2013-04-29 17:01 ` Alex Williamson
2013-04-29 16:49 ` Alex Williamson
2013-04-29 16:05 ` Randy Dunlap [this message]
2013-04-30 16:36 ` [PATCH -next] proc_fs.h: fix build error when PROC_FS is not enabled David Rientjes
2013-04-30 17:40 ` Randy Dunlap
2013-04-29 16:05 ` [PATCH -next] tty.h: fix build errors " Randy Dunlap
2013-04-30 16:39 ` David Rientjes
2013-04-29 16:17 ` linux-next: Tree for Apr 29 (include/linux/proc_fs.h: proc_net_mkdir) Randy Dunlap
2013-04-29 16:25 ` linux-next: Tree for Apr 29 (kconfig) Randy Dunlap
2013-04-29 17:42 ` Yann E. MORIN
2013-04-29 16:42 ` linux-next: Tree for Apr 29 (staging/gdm72xx) Randy Dunlap
2013-04-29 16:51 ` linux-next: Tree for Apr 29 (sound/soc) Randy Dunlap
2013-04-29 17:13 ` linux-next: Tree for Apr 29 (many build errors when PROC_FS is not set -- part 1) Randy Dunlap
2013-04-29 20:05 ` linux-next: Tree for Apr 29 Randy Dunlap
2013-04-29 20:05 ` Randy Dunlap
2013-04-29 21:03 ` Randy Dunlap
2013-04-29 21:03 ` Randy Dunlap
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=517E9A49.5080106@infradead.org \
--to=rdunlap@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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.