From: "Darrick J. Wong" <djwong@kernel.org>
To: long.yunjian@zte.com.cn
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
mou.yi@zte.com.cn, zhang.xianwei8@zte.com.cn,
ouyang.maochun@zte.com.cn, jiang.xuexin@zte.com.cn,
lv.mengzhao@zte.com.cn, xu.lifeng1@zte.com.cn,
yang.yang29@zte.com.cn
Subject: Re: [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty"
Date: Sat, 15 Mar 2025 11:30:35 -0700 [thread overview]
Message-ID: <20250315183035.GA2803749@frogsfrogsfrogs> (raw)
In-Reply-To: <20250315143216175uf7xlZ4jkOfP5o3oxuM4z@zte.com.cn>
On Sat, Mar 15, 2025 at 02:32:16PM +0800, long.yunjian@zte.com.cn wrote:
> From: Zhang Xianwei <zhang.xianwei8@zte.com.cn>
>
> There is a spelling mistake in fs/xfs/xfs_log.c. Fix it.
>
> Signed-off-by: Zhang Xianwei <zhang.xianwei8@zte.com.cn>
Looks ok,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> v1 -> v2
> fix the format of this patch
> fs/xfs/xfs_log.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index f8851ff835de..ba700785759a 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2887,7 +2887,7 @@ xlog_force_and_check_iclog(
> *
> * 1. the current iclog is active and has no data; the previous iclog
> * is in the active or dirty state.
> - * 2. the current iclog is drity, and the previous iclog is in the
> + * 2. the current iclog is dirty, and the previous iclog is in the
> * active or dirty state.
> *
> * We may sleep if:
> --
> 2.27.0
>
next prev parent reply other threads:[~2025-03-15 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 6:32 [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty" long.yunjian
2025-03-15 18:30 ` Darrick J. Wong [this message]
2025-04-16 8:45 ` 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=20250315183035.GA2803749@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=long.yunjian@zte.com.cn \
--cc=lv.mengzhao@zte.com.cn \
--cc=mou.yi@zte.com.cn \
--cc=ouyang.maochun@zte.com.cn \
--cc=xu.lifeng1@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=zhang.xianwei8@zte.com.cn \
/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