public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty"
@ 2025-03-15  6:32 long.yunjian
  2025-03-15 18:30 ` Darrick J. Wong
  2025-04-16  8:45 ` Carlos Maiolino
  0 siblings, 2 replies; 3+ messages in thread
From: long.yunjian @ 2025-03-15  6:32 UTC (permalink / raw)
  To: djwong
  Cc: djwong, linux-xfs, linux-kernel, mou.yi, zhang.xianwei8,
	ouyang.maochun, jiang.xuexin, lv.mengzhao, xu.lifeng1,
	yang.yang29

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>
---
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

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty"
  2025-03-15  6:32 [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty" long.yunjian
@ 2025-03-15 18:30 ` Darrick J. Wong
  2025-04-16  8:45 ` Carlos Maiolino
  1 sibling, 0 replies; 3+ messages in thread
From: Darrick J. Wong @ 2025-03-15 18:30 UTC (permalink / raw)
  To: long.yunjian
  Cc: linux-xfs, linux-kernel, mou.yi, zhang.xianwei8, ouyang.maochun,
	jiang.xuexin, lv.mengzhao, xu.lifeng1, yang.yang29

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
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty"
  2025-03-15  6:32 [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty" long.yunjian
  2025-03-15 18:30 ` Darrick J. Wong
@ 2025-04-16  8:45 ` Carlos Maiolino
  1 sibling, 0 replies; 3+ messages in thread
From: Carlos Maiolino @ 2025-04-16  8:45 UTC (permalink / raw)
  To: djwong, long.yunjian
  Cc: djwong, linux-xfs, linux-kernel, mou.yi, zhang.xianwei8,
	ouyang.maochun, jiang.xuexin, lv.mengzhao, xu.lifeng1,
	yang.yang29

On Sat, 15 Mar 2025 14:32:16 +0800, long.yunjian@zte.com.cn wrote:
> There is a spelling mistake in fs/xfs/xfs_log.c. Fix it.
> 
> 

Applied to for-next, thanks!

[1/1] xfs: Fix spelling mistake "drity" -> "dirty"
      commit: 1c406526bd84f1e0bd4bb4b50c6eeba0b135765a

Best regards,
-- 
Carlos Maiolino <cem@kernel.org>


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-04-16  8:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-15  6:32 [PATCH v2] xfs: Fix spelling mistake "drity" -> "dirty" long.yunjian
2025-03-15 18:30 ` Darrick J. Wong
2025-04-16  8:45 ` Carlos Maiolino

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox