All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Nidhish Chauhan <solemnsquire@gmail.com>
Cc: linux-kernel-mentees@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: filesystems: removed repeated word
Date: Thu, 22 May 2025 16:20:38 -0600	[thread overview]
Message-ID: <2973cc3d-a4e2-4120-ae89-730581090ef8@linuxfoundation.org> (raw)
In-Reply-To: <20250516164648.15396-1-solemnsquire@gmail.com>

On 5/16/25 10:46, Nidhish Chauhan wrote:
> Removed a repeated word 'at' from journalling.rst at line no. 96 in
> filesystems directory.
> 
> Signed-off-by: Nidhish Chauhan <solemnsquire@gmail.com>
> ---
>   Documentation/filesystems/journalling.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/filesystems/journalling.rst b/Documentation/filesystems/journalling.rst
> index 863e93e623f7..2825f6c030c2 100644
> --- a/Documentation/filesystems/journalling.rst
> +++ b/Documentation/filesystems/journalling.rst
> @@ -93,7 +93,7 @@ easily as on jbd2_journal_start().
>   
>   Try to reserve the right number of blocks the first time. ;-). This will
>   be the maximum number of blocks you are going to touch in this
> -transaction. I advise having a look at at least ext4_jbd.h to see the
> +transaction. I advise having a look at least ext4_jbd.h to see the
>   basis on which ext4 uses to make these decisions.
>   
>   Another wriggle to watch out for is your on-disk block allocation

Please run get_maintainers.pl to get the correct list of recipients for
this patch.

thanks,
-- Shuah

  reply	other threads:[~2025-05-22 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 16:46 [PATCH] docs: filesystems: removed repeated word Nidhish Chauhan
2025-05-22 22:20 ` Shuah Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-22 23:11 Nidhish Chauhan

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=2973cc3d-a4e2-4120-ae89-730581090ef8@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solemnsquire@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.