From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-next@vger.kernel.org
Cc: akpm <akpm@linux-foundation.org>, viro@zeniv.linux.org.uk
Subject: [PATCH -next] fs: fix inode.c kernel-doc warnings
Date: Wed, 22 Oct 2008 16:39:47 -0700 [thread overview]
Message-ID: <48FFB9C3.1000703@xenotime.net> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix fs/inode.c kernel-doc warnings:
Warning(linux-next-20081022//fs/inode.c:120): No description found for parameter 'sb'
Warning(linux-next-20081022//fs/inode.c:120): No description found for parameter 'inode'
Warning(linux-next-20081022//fs/inode.c:587): No description found for parameter 'sb'
Warning(linux-next-20081022//fs/inode.c:587): No description found for parameter 'inode'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
cc: Al Viro <viro@zeniv.linux.org.uk>
---
fs/inode.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- linux-next-20081022.orig/fs/inode.c
+++ linux-next-20081022/fs/inode.c
@@ -110,8 +110,8 @@ static void wake_up_inode(struct inode *
/**
* inode_init_always - perform inode structure intialisation
- * @sb - superblock inode belongs to.
- * @inode - inode to initialise
+ * @sb: superblock inode belongs to.
+ * @inode: inode to initialise
*
* These are initializations that need to be done on every inode
* allocation as the fields are not initialised by slab allocation.
@@ -573,8 +573,8 @@ __inode_add_to_lists(struct super_block
/**
* inode_add_to_lists - add a new inode to relevant lists
- * @sb - superblock inode belongs to.
- * @inode - inode to mark in use
+ * @sb: superblock inode belongs to.
+ * @inode: inode to mark in use
*
* When an inode is allocated it needs to be accounted for, added to the in use
* list, the owning superblock and the inode hash. This needs to be done under
reply other threads:[~2008-10-22 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48FFB9C3.1000703@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).