From: domen@coderock.org
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel@vger.kernel.org, domen@coderock.org
Subject: [patch 5/5] fs/super.c: docbook comment fix
Date: Mon, 10 Jan 2005 19:45:36 +0100 [thread overview]
Message-ID: <20050110184537.4FDBF1F1ED@trashy.coderock.org> (raw)
Parameter name in comment was wrong.
Compile tested.
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/fs/super.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/super.c~docs-fs_super fs/super.c
--- kj/fs/super.c~docs-fs_super 2005-01-10 18:00:27.000000000 +0100
+++ kj-domen/fs/super.c 2005-01-10 18:00:27.000000000 +0100
@@ -143,7 +143,7 @@ int __put_super_and_need_restart(struct
/**
* put_super - drop a temporary reference to superblock
- * @s: superblock in question
+ * @sb: superblock in question
*
* Drops a temporary reference, frees superblock if there's no
* references left.
_
reply other threads:[~2005-01-10 18:52 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=20050110184537.4FDBF1F1ED@trashy.coderock.org \
--to=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.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).