[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240317154951.GB1927156@frogsfrogsfrogs>
Date: Sun, 17 Mar 2024 08:49:51 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Thorsten Blum <thorsten.blum@...lux.com>
Cc: Chandan Babu R <chandan.babu@...cle.com>, linux-xfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] xfs: Fix typo in comment
On Sun, Mar 17, 2024 at 04:47:32PM +0100, Thorsten Blum wrote:
> s/somethign/something/
>
> Signed-off-by: Thorsten Blum <thorsten.blum@...lux.com>
Reviewed-by: Darrick J. Wong <djwong@...nel.org>
--D
> ---
> 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
>
>
Powered by blists - more mailing lists