summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorHitoshi Mitake <mitake@dcl.info.waseda.ac.jp>2009-06-22 11:11:20 +0900
committerLinus Torvalds <torvalds@linux-foundation.org>2009-06-22 11:34:42 -0700
commite38be994b9cad09b0d8d78a1875d7e8a2e115d29 (patch)
tree5f2e4ab8585c9a5d70cbe50abf7345d989cbb57c
parent44da59e4006fbf7c4cc9b54485a37a40726091ee (diff)
downloadop-kernel-dev-e38be994b9cad09b0d8d78a1875d7e8a2e115d29.zip
op-kernel-dev-e38be994b9cad09b0d8d78a1875d7e8a2e115d29.tar.gz
Making fs/minix/minix.h double including safe
I happened to find that fs/minix/minix.h doesn't guard double include. Yes, I know this never cause something destructive because this is self-evidence that no source file includes minix.h twice, but I think fixing this is better than disregarding it. Signed-off-by: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--fs/minix/minix.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/fs/minix/minix.h b/fs/minix/minix.h
index cb7fdd1..9dcf95b 100644
--- a/fs/minix/minix.h
+++ b/fs/minix/minix.h
@@ -1,3 +1,6 @@
+#ifndef FS_MINIX_H
+#define FS_MINIX_H
+
#include <linux/fs.h>
#include <linux/pagemap.h>
#include <linux/minix_fs.h>
@@ -86,3 +89,5 @@ static inline struct minix_inode_info *minix_i(struct inode *inode)
{
return list_entry(inode, struct minix_inode_info, vfs_inode);
}
+
+#endif /* FS_MINIX_H */
OpenPOWER on IntegriCloud