Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Md Shofiqul Islam <shofiqtest@gmail.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	 djwong@kernel.org
Subject: Re: [PATCH v2] xfs: Fix typo in comment
Date: Mon, 11 May 2026 12:58:29 +0200	[thread overview]
Message-ID: <agG2J_aQvgsACdyA@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260506163658.2318-1-shofiqtest@gmail.com>

On Wed, May 06, 2026 at 07:36:58PM +0300, Md Shofiqul Islam wrote:
> Fix spelling mistake in comment:
>  - occured -> occurred
> 
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> Signed-off-by: Md Shofiqul Islam <shofiqtest@gmail.com>

FWIW you don't need to send a V2 if there is nothing to change just to
add a RwB tag.

> ---
>  fs/xfs/xfs_notify_failure.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_notify_failure.c b/fs/xfs/xfs_notify_failure.c
> index 64c8afb935..b994ff15d5 100644
> --- a/fs/xfs/xfs_notify_failure.c
> +++ b/fs/xfs/xfs_notify_failure.c
> @@ -350,7 +350,7 @@ xfs_dax_notify_dev_failure(
>  	/*
>  	 * Shutdown fs from a force umount in pre-remove case which won't fail,
>  	 * so errors can be ignored.  Otherwise, shutdown the filesystem with
> -	 * CORRUPT flag if error occured or notify.want_shutdown was set during
> +	 * CORRUPT flag if error occurred or notify.want_shutdown was set during
>  	 * RMAP querying.
>  	 */
>  	if (mf_flags & MF_MEM_PRE_REMOVE)
> --
> 2.54.0.windows.1

  reply	other threads:[~2026-05-11 10:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C6jMuZzoBJA4hY9WiBIKpBD0eZNBS6RFki07XHjwG5uYm7IGIWOb4perbBt7yiEgMzoaa6Q-RmYr4CpOoMp3vA==@protonmail.internalid>
2026-05-06 16:36 ` [PATCH v2] xfs: Fix typo in comment Md Shofiqul Islam
2026-05-11 10:58   ` Carlos Maiolino [this message]
2026-05-12 12:08   ` Carlos Maiolino

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=agG2J_aQvgsACdyA@nidhogg.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=shofiqtest@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