public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>,
	linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
	linux-kernel-mentees@lists.linux.dev,
	Suchit Karunakaran <suchitkarunakaran@gmail.com>
Subject: Re: [PATCH] docs: debugfs: fix spelling of "failure"
Date: Tue, 04 Mar 2025 09:40:46 -0700	[thread overview]
Message-ID: <87a5a0eokx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250220171903.11321-1-suchitkarunakaran@gmail.com>

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

      reply	other threads:[~2025-03-04 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 17:19 [PATCH] docs: debugfs: fix spelling of "failure" Suchit Karunakaran
2025-03-04 16:40 ` Jonathan Corbet [this message]

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=87a5a0eokx.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=suchitkarunakaran@gmail.com \
    /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