From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: jaharkes@cs.cmu.edu, linux-kernel@vger.kernel.org
Subject: [2.6 patch] fs/coda/: proper prototypes
Date: Sun, 29 Jan 2006 00:04:49 +0100 [thread overview]
Message-ID: <20060128230449.GU3777@stusta.de> (raw)
This patch introduces a file fs/coda/coda_int.h with proper prototypes
for some code.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Acked-by: Jan Harkes <jaharkes@cs.cmu.edu>
---
This patch was already sent on:
- 21 Jan 2006
fs/coda/coda_int.h | 13 +++++++++++++
fs/coda/dir.c | 3 ++-
fs/coda/file.c | 2 ++
fs/coda/inode.c | 2 ++
fs/coda/psdev.c | 9 ++-------
5 files changed, 21 insertions(+), 8 deletions(-)
--- /dev/null 2005-11-08 19:07:57.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/fs/coda/coda_int.h 2006-01-21 01:06:23.000000000 +0100
@@ -0,0 +1,13 @@
+#ifndef _CODA_INT_
+#define _CODA_INT_
+
+extern struct file_system_type coda_fs_type;
+
+void coda_destroy_inodecache(void);
+int coda_init_inodecache(void);
+int coda_fsync(struct file *coda_file, struct dentry *coda_dentry,
+ int datasync);
+
+#endif /* _CODA_INT_ */
+
+
--- linux-2.6.16-rc1-mm2-full/fs/coda/file.c.old 2006-01-21 01:02:36.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/fs/coda/file.c 2006-01-21 01:02:51.000000000 +0100
@@ -24,6 +24,8 @@
#include <linux/coda_psdev.h>
#include <linux/coda_proc.h>
+#include "coda_int.h"
+
/* if CODA_STORE fails with EOPNOTSUPP, venus clearly doesn't support
* CODA_STORE/CODA_RELEASE and we fall back on using the CODA_CLOSE upcall */
static int use_coda_close;
--- linux-2.6.16-rc1-mm2-full/fs/coda/dir.c.old 2006-01-21 01:03:33.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/fs/coda/dir.c 2006-01-21 01:03:57.000000000 +0100
@@ -27,6 +27,8 @@
#include <linux/coda_cache.h>
#include <linux/coda_proc.h>
+#include "coda_int.h"
+
/* dir inode-ops */
static int coda_create(struct inode *dir, struct dentry *new, int mode, struct nameidata *nd);
static struct dentry *coda_lookup(struct inode *dir, struct dentry *target, struct nameidata *nd);
@@ -50,7 +52,6 @@
/* support routines */
static int coda_venus_readdir(struct file *filp, filldir_t filldir,
void *dirent, struct dentry *dir);
-int coda_fsync(struct file *, struct dentry *dentry, int datasync);
/* same as fs/bad_inode.c */
static int coda_return_EIO(void)
--- linux-2.6.16-rc1-mm2-full/fs/coda/inode.c.old 2006-01-21 01:04:12.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/fs/coda/inode.c 2006-01-21 01:04:28.000000000 +0100
@@ -31,6 +31,8 @@
#include <linux/coda_fs_i.h>
#include <linux/coda_cache.h>
+#include "coda_int.h"
+
/* VFS super_block ops */
static void coda_clear_inode(struct inode *);
static void coda_put_super(struct super_block *);
--- linux-2.6.16-rc1-mm2-full/fs/coda/psdev.c.old 2006-01-21 01:04:36.000000000 +0100
+++ linux-2.6.16-rc1-mm2-full/fs/coda/psdev.c 2006-01-21 01:06:07.000000000 +0100
@@ -48,12 +48,9 @@
#include <linux/coda_psdev.h>
#include <linux/coda_proc.h>
-#define upc_free(r) kfree(r)
+#include "coda_int.h"
-/*
- * Coda stuff
- */
-extern struct file_system_type coda_fs_type;
+#define upc_free(r) kfree(r)
/* statistics */
int coda_hard; /* allows signals during upcalls */
@@ -394,8 +391,6 @@
MODULE_AUTHOR("Peter J. Braam <braam@cs.cmu.edu>");
MODULE_LICENSE("GPL");
-extern int coda_init_inodecache(void);
-extern void coda_destroy_inodecache(void);
static int __init init_coda(void)
{
int status;
next reply other threads:[~2006-01-28 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 23:04 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 0:35 [2.6 patch] fs/coda/: proper prototypes Adrian Bunk
2006-01-23 0:15 ` Jan Harkes
2006-01-23 0:36 ` Adrian Bunk
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=20060128230449.GU3777@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/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.