[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20210607014933.20329-1-lijian_8010a29@163.com>
Date: Mon, 7 Jun 2021 09:49:33 +0800
From: lijian_8010a29@....com
To: viro@...iv.linux.org.uk
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
lijian <lijian@...ong.com>
Subject: [PATCH] fs: namei: deleted the repeated word
From: lijian <lijian@...ong.com>
deleted the repeated word 'to' in the comments
Signed-off-by: lijian <lijian@...ong.com>
---
fs/namei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/namei.c b/fs/namei.c
index 79b0ff9b151e..4062c00827fd 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -770,7 +770,7 @@ static bool try_to_unlazy(struct nameidata *nd)
* @seq: seq number to check @dentry against
* Returns: true on success, false on failure
*
- * Similar to to try_to_unlazy(), but here we have the next dentry already
+ * Similar to try_to_unlazy(), but here we have the next dentry already
* picked by rcu-walk and want to legitimize that in addition to the current
* nd->path and nd->root for ref-walk mode. Must be called from rcu-walk context.
* Nothing should touch nameidata between try_to_unlazy_next() failure and
--
2.25.1
Powered by blists - more mailing lists