Documentation/filesystems/debugfs.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Fix a typo in debugfs documentation where "failure" was misspelled
as "failuer".
Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
---
Documentation/filesystems/debugfs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/debugfs.rst b/Documentation/filesystems/debugfs.rst
index f7f977ffbf8d..610f718ef8b5 100644
--- a/Documentation/filesystems/debugfs.rst
+++ b/Documentation/filesystems/debugfs.rst
@@ -220,7 +220,7 @@ There are a couple of other directory-oriented helper functions::
A call to debugfs_change_name() will give a new name to an existing debugfs
file, always in the same directory. The new_name must not exist prior
-to the call; the return value is 0 on success and -E... on failuer.
+to the call; the return value is 0 on success and -E... on failure.
Symbolic links can be created with debugfs_create_symlink().
There is one important thing that all debugfs users must take into account:
--
2.48.1
Suchit Karunakaran <suchitkarunakaran@gmail.com> writes: > Fix a typo in debugfs documentation where "failure" was misspelled > as "failuer". > > Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com> > --- > Documentation/filesystems/debugfs.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/filesystems/debugfs.rst b/Documentation/filesystems/debugfs.rst > index f7f977ffbf8d..610f718ef8b5 100644 > --- a/Documentation/filesystems/debugfs.rst > +++ b/Documentation/filesystems/debugfs.rst > @@ -220,7 +220,7 @@ There are a couple of other directory-oriented helper functions:: > > A call to debugfs_change_name() will give a new name to an existing debugfs > file, always in the same directory. The new_name must not exist prior > -to the call; the return value is 0 on success and -E... on failuer. > +to the call; the return value is 0 on success and -E... on failure. > Symbolic links can be created with debugfs_create_symlink(). This was already fixed (along with several other similar mistakes) in early February. Thanks, jon
© 2016 - 2025 Red Hat, Inc.