From: "Darrick J. Wong" <djwong@kernel.org>
To: Md Shofiqul Islam <shofiqtest@gmail.com>
Cc: linux-xfs@vger.kernel.org, cem@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Fix typo in comment
Date: Tue, 5 May 2026 16:04:47 -0700 [thread overview]
Message-ID: <20260505230447.GI7751@frogsfrogsfrogs> (raw)
In-Reply-To: <20260505225044.6484-1-shofiqtest@gmail.com>
On Wed, May 06, 2026 at 01:50:44AM +0300, Md Shofiqul Islam wrote:
> Fix spelling mistake in comment:
> - occured -> occurred
> ---
> 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 64c8afb93..b994ff15d 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
It occured to me that although this is a small change, it is technically
correct. ;)
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> * RMAP querying.
> */
> if (mf_flags & MF_MEM_PRE_REMOVE)
> --
> 2.51.1
>
>
next prev parent reply other threads:[~2026-05-05 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 22:50 [PATCH] xfs: Fix typo in comment Md Shofiqul Islam
2026-05-05 23:04 ` Darrick J. Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 15:47 Thorsten Blum
2024-03-17 15:49 ` Darrick J. Wong
2024-03-17 21:12 ` Christoph Hellwig
2024-03-17 21:53 ` Randy Dunlap
2024-03-17 23:34 ` Thorsten Blum
2024-03-17 23:46 ` Randy Dunlap
2022-05-21 11:11 [PATCH] xfs: fix " Julia Lawall
2022-05-21 19:25 ` Darrick J. Wong
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=20260505230447.GI7751@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@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