summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/data.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk.kim@samsung.com>2012-11-29 13:28:09 +0900
committerJaegeuk Kim <jaegeuk.kim@samsung.com>2012-12-11 13:43:42 +0900
commit0a8165d7c2cf1395059db20ab07665baf3758fcd (patch)
tree6036856230364c8301db6798bb442f44e608a098 /fs/f2fs/data.c
parent25ca923b2a766b9c93b63777ead351137533a623 (diff)
downloadop-kernel-dev-0a8165d7c2cf1395059db20ab07665baf3758fcd.zip
op-kernel-dev-0a8165d7c2cf1395059db20ab07665baf3758fcd.tar.gz
f2fs: adjust kernel coding style
As pointed out by Randy Dunlap, this patch removes all usage of "/**" for comment blocks. Instead, just use "/*". Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs/f2fs/data.c')
-rw-r--r--fs/f2fs/data.c12
1 files changed, 6 insertions, 6 deletions
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 5635cc5..444c2a6 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -1,4 +1,4 @@
-/**
+/*
* fs/f2fs/data.c
*
* Copyright (c) 2012 Samsung Electronics Co., Ltd.
@@ -21,7 +21,7 @@
#include "node.h"
#include "segment.h"
-/**
+/*
* Lock ordering for the change of data block address:
* ->data_page
* ->node_page
@@ -207,7 +207,7 @@ struct page *find_data_page(struct inode *inode, pgoff_t index)
return page;
}
-/**
+/*
* If it tries to access a hole, return an error.
* Because, the callers, functions in dir.c and GC, should be able to know
* whether this page exists or not.
@@ -247,7 +247,7 @@ struct page *get_lock_data_page(struct inode *inode, pgoff_t index)
return page;
}
-/**
+/*
* Caller ensures that this data page is never allocated.
* A new zero-filled data page is allocated in the page cache.
*/
@@ -322,7 +322,7 @@ static void read_end_io(struct bio *bio, int err)
bio_put(bio);
}
-/**
+/*
* Fill the locked page with data located in the block address.
* Read operation is synchronous, and caller must unlock the page.
*/
@@ -367,7 +367,7 @@ int f2fs_readpage(struct f2fs_sb_info *sbi, struct page *page,
return 0;
}
-/**
+/*
* This function should be used by the data read flow only where it
* does not check the "create" flag that indicates block allocation.
* The reason for this special functionality is to exploit VFS readahead
OpenPOWER on IntegriCloud