svn commit: r279537 - head/sys/fs/fuse

[Jung-uk Kim]

Author: jkim
Date: Mon Mar  2 19:14:58 2015
New Revision: 279537
URL: https://svnweb.freebsd.org/changeset/base/279537

Log:
  Fix white spaces.

Modified:
  head/sys/fs/fuse/fuse_node.c

Modified: head/sys/fs/fuse/fuse_node.c
==============================================================================
--- head/sys/fs/fuse/fuse_node.c	Mon Mar  2 19:04:27 2015	(r279536)
+++ head/sys/fs/fuse/fuse_node.c	Mon Mar  2 19:14:58 2015	(r279537)
@@ -270,24 +270,24 @@ void
 fuse_vnode_open(struct vnode *vp, int32_t fuse_open_flags, struct thread *td)
 {
 	/*
-         * Funcation is called for every vnode open.
-         * Merge fuse_open_flags it may be 0
-         *
-         * XXXIP: Handle FOPEN_KEEP_CACHE
-         */
-        /*
-	  * Ideally speaking, direct io should be enabled on
-         * fd's but do not see of any way of providing that
-         * this implementation.
-
-         * Also cannot think of a reason why would two
-         * different fd's on same vnode would like
-         * have DIRECT_IO turned on and off. But linux
-         * based implementation works on an fd not an
-         * inode and provides such a feature.
-         *
-         * XXXIP: Handle fd based DIRECT_IO
-         */
+	 * Funcation is called for every vnode open.
+	 * Merge fuse_open_flags it may be 0
+	 *
+	 * XXXIP: Handle FOPEN_KEEP_CACHE
+	 */
+	/*
+	 * Ideally speaking, direct io should be enabled on
+	 * fd's but do not see of any way of providing that
+	 * this implementation.
+	 *
+	 * Also cannot think of a reason why would two
+	 * different fd's on same vnode would like
+	 * have DIRECT_IO turned on and off. But linux
+	 * based implementation works on an fd not an
+	 * inode and provides such a feature.
+	 *
+	 * XXXIP: Handle fd based DIRECT_IO
+	 */
 	if (fuse_open_flags & FOPEN_DIRECT_IO) {
 		VTOFUD(vp)->flag |= FN_DIRECTIO;
 	} else {