From: qiwuchen55@gmail.com
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, chenqiwu <chenqiwu@xiaomi.com>
Subject: [PATCH] fs: update comment for current parameters
Date: Sun, 9 Feb 2020 10:35:06 +0800 [thread overview]
Message-ID: <1581215706-30750-1-git-send-email-qiwuchen55@gmail.com> (raw)
From: chenqiwu <chenqiwu@xiaomi.com>
Update the comment of current parameters for attach_recursive_mnt()
and propagate_mnt().
Signed-off-by: chenqiwu <chenqiwu@xiaomi.com>
---
fs/namespace.c | 8 +++++---
fs/pnode.c | 2 +-
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/namespace.c b/fs/namespace.c
index 85b5f7b..3332a9c 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -1975,9 +1975,11 @@ int count_mounts(struct mnt_namespace *ns, struct mount *mnt)
}
/*
- * @source_mnt : mount tree to be attached
- * @nd : place the mount tree @source_mnt is attached
- * @parent_nd : if non-null, detach the source_mnt from its parent and
+ * attach_recursive_mnt - attach a source mount to a destination mount.
+ * @source_mnt : source mount.
+ * @dest_mnt : destination mount.
+ * @dest_mp : destination mountpoint.
+ * @moving : if true, detach the source_mnt from its parent and
* store the parent mount and mountpoint dentry.
* (done when source_mnt is moved)
*
diff --git a/fs/pnode.c b/fs/pnode.c
index 49f6d7f..bc378ec 100644
--- a/fs/pnode.c
+++ b/fs/pnode.c
@@ -282,7 +282,7 @@ static int propagate_one(struct mount *m)
* headed at source_mnt's ->mnt_list
*
* @dest_mnt: destination mount.
- * @dest_dentry: destination dentry.
+ * @dest_mp: destination mountpoint.
* @source_mnt: source mount.
* @tree_list : list of heads of trees to be attached.
*/
--
1.9.1
reply other threads:[~2020-02-09 2:35 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=1581215706-30750-1-git-send-email-qiwuchen55@gmail.com \
--to=qiwuchen55@gmail.com \
--cc=chenqiwu@xiaomi.com \
--cc=linux-fsdevel@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).