2024-03-17 23:46:19

by Randy Dunlap

[permalink] [raw]
Subject: Re: [PATCH] xfs: Fix typo in comment



On 3/17/24 16:34, Thorsten Blum wrote:
> On 17. Mar 2024, at 22:53, Randy Dunlap <[email protected]> wrote:
>>
>> Also s/straight away/straightaway/
>
> Apparently, both are grammatically correct.

OK :)

--
#Randy


2024-04-12 23:00:08

by Thorsten Blum

[permalink] [raw]
Subject: [RESEND PATCH] xfs: Fix typo in comment

s/somethign/something/

Signed-off-by: Thorsten Blum <[email protected]>
Reviewed-by: Darrick J. Wong <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
---
fs/xfs/xfs_log_priv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/xfs_log_priv.h b/fs/xfs/xfs_log_priv.h
index e30c06ec20e3..25b6d6cdd545 100644
--- a/fs/xfs/xfs_log_priv.h
+++ b/fs/xfs/xfs_log_priv.h
@@ -683,7 +683,7 @@ xlog_valid_lsn(
* flags to control the kmalloc() behaviour within kvmalloc(). Hence kmalloc()
* will do direct reclaim and compaction in the slow path, both of which are
* horrendously expensive. We just want kmalloc to fail fast and fall back to
- * vmalloc if it can't get somethign straight away from the free lists or
+ * vmalloc if it can't get something straight away from the free lists or
* buddy allocator. Hence we have to open code kvmalloc outselves here.
*
* This assumes that the caller uses memalloc_nofs_save task context here, so
--
2.44.0