The patch titled
fs/coda: remove static inline forward declarations
has been added to the -mm tree. Its filename is
fs-coda-remove-static-inline-forward-declarations.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fs/coda: remove static inline forward declarations
From: Ilpo Järvinen <[EMAIL PROTECTED]>
They're defined later on in the same file with bodies and nothing in
between needs them.
Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]>
Reviewed-by: Pekka Enberg <[EMAIL PROTECTED]>
Acked-by: Jan Harkes <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
include/linux/coda_linux.h | 3 ---
1 file changed, 3 deletions(-)
diff -puN
include/linux/coda_linux.h~fs-coda-remove-static-inline-forward-declarations
include/linux/coda_linux.h
---
a/include/linux/coda_linux.h~fs-coda-remove-static-inline-forward-declarations
+++ a/include/linux/coda_linux.h
@@ -43,9 +43,6 @@ int coda_getattr(struct vfsmount *, stru
int coda_setattr(struct dentry *, struct iattr *);
/* this file: heloers */
-static __inline__ struct CodaFid *coda_i2f(struct inode *);
-static __inline__ char *coda_i2s(struct inode *);
-static __inline__ void coda_flag_inode(struct inode *, int flag);
char *coda_f2s(struct CodaFid *f);
int coda_isroot(struct inode *i);
int coda_iscontrol(const char *name, size_t length);
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
origin.patch
fs-coda-remove-static-inline-forward-declarations.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
