From: "Darrick J. Wong" <djwong@kernel.org>
To: Thorsten Blum <thorsten.blum@toblux.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Fix typo in comment
Date: Sun, 17 Mar 2024 08:49:51 -0700 [thread overview]
Message-ID: <20240317154951.GB1927156@frogsfrogsfrogs> (raw)
In-Reply-To: <20240317154731.2801-2-thorsten.blum@toblux.com>
On Sun, Mar 17, 2024 at 04:47:32PM +0100, Thorsten Blum wrote:
> s/somethign/something/
>
> Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.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
>
>
next prev parent reply other threads:[~2024-03-17 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 15:47 Thorsten Blum
2024-03-17 15:49 ` Darrick J. Wong [this message]
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
2024-04-12 22:59 ` [RESEND PATCH] " Thorsten Blum
-- strict thread matches above, loose matches on Subject: below --
2026-05-05 22:50 [PATCH] " Md Shofiqul Islam
2026-05-05 23:04 ` Darrick J. Wong
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=20240317154951.GB1927156@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=thorsten.blum@toblux.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
all inboxes | Powered by JetHome®