[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220125131340.1109125-1-trix@redhat.com>
Date: Tue, 25 Jan 2022 05:13:40 -0800
From: trix@...hat.com
To: viro@...iv.linux.org.uk
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Tom Rix <trix@...hat.com>
Subject: [PATCH] namei: cleanup double word in comment
From: Tom Rix <trix@...hat.com>
Remove the second 'to'.
Signed-off-by: Tom Rix <trix@...hat.com>
---
fs/namei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/namei.c b/fs/namei.c
index fa9be370c6702..61c87d4cdc5cd 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -797,7 +797,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.26.3
Powered by blists - more mailing lists