diff options
author | jkim <jkim@FreeBSD.org> | 2015-03-02 19:14:58 +0000 |
---|---|---|
committer | jkim <jkim@FreeBSD.org> | 2015-03-02 19:14:58 +0000 |
commit | d07e2757d919ad93856db72cb57806ca09d4a3e2 (patch) | |
tree | 2c7fdea365478cd883d6e23ad6e64a7760b02da1 | |
parent | ab90d82e08b6f72ac1c5ada979be655bba042381 (diff) | |
download | FreeBSD-src-d07e2757d919ad93856db72cb57806ca09d4a3e2.zip FreeBSD-src-d07e2757d919ad93856db72cb57806ca09d4a3e2.tar.gz |
Fix white spaces.
-rw-r--r-- | sys/fs/fuse/fuse_node.c | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/sys/fs/fuse/fuse_node.c b/sys/fs/fuse/fuse_node.c index a6119dd..2d9a538 100644 --- a/sys/fs/fuse/fuse_node.c +++ b/sys/fs/fuse/fuse_node.c @@ -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 { |