summaryrefslogtreecommitdiff
path: root/fs/jbd
diff options
context:
space:
mode:
authorRandy Dunlap <rdunlap@xenotime.net>2005-11-07 01:01:04 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2005-11-07 07:53:55 -0800
commit6c8bec6d5f24b01c53b792b06a645e78d482020d (patch)
treed394d7d77087c02f84f84a27d3e9933d9c096bed /fs/jbd
parent2500e7abc8f606d87b2590f205dac080640b6b04 (diff)
downloadlinux-3.10-6c8bec6d5f24b01c53b792b06a645e78d482020d.tar.gz
linux-3.10-6c8bec6d5f24b01c53b792b06a645e78d482020d.tar.bz2
linux-3.10-6c8bec6d5f24b01c53b792b06a645e78d482020d.zip
[PATCH] jbd doc: fix some kernel-doc warnings
Add structure fields kernel-doc for 2 fields in struct journal_s. Warning(/var/linsrc/linux-2614-rc4//include/linux/jbd.h:808): No description found for parameter 'j_wbuf' Warning(/var/linsrc/linux-2614-rc4//include/linux/jbd.h:808): No description found for parameter 'j_wbufsize' Convert fs/jbd/recovery.c non-static functions to kernel-doc format. fs/jbd/recovery.c doesn't export any symbols, so it should use !I instead of !E to eliminate this warning message: Warning(/var/linsrc/linux-2614-rc4//fs/jbd/recovery.c): no structured comments found Signed-off-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'fs/jbd')
-rw-r--r--fs/jbd/recovery.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/jbd/recovery.c b/fs/jbd/recovery.c
index 103c34e4fb2..80d7f53fd0a 100644
--- a/fs/jbd/recovery.c
+++ b/fs/jbd/recovery.c
@@ -210,7 +210,7 @@ do { \
} while (0)
/**
- * int journal_recover(journal_t *journal) - recovers a on-disk journal
+ * journal_recover - recovers a on-disk journal
* @journal: the journal to recover
*
* The primary function for recovering the log contents when mounting a
@@ -266,7 +266,7 @@ int journal_recover(journal_t *journal)
}
/**
- * int journal_skip_recovery() - Start journal and wipe exiting records
+ * journal_skip_recovery - Start journal and wipe exiting records
* @journal: journal to startup
*
* Locate any valid recovery information from the journal and set up the