From: Thorsten Blum <thorsten.blum@toblux.com>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Blum <thorsten.blum@toblux.com>
Subject: [PATCH] xfs: Fix typo in comment
Date: Sun, 17 Mar 2024 16:47:32 +0100 [thread overview]
Message-ID: <20240317154731.2801-2-thorsten.blum@toblux.com> (raw)
s/somethign/something/
Signed-off-by: Thorsten Blum <thorsten.blum@toblux.com>
---
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 reply other threads:[~2024-03-17 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 15:47 Thorsten Blum [this message]
2024-03-17 15:49 ` [PATCH] xfs: Fix typo in comment Darrick J. Wong
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 --
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=20240317154731.2801-2-thorsten.blum@toblux.com \
--to=thorsten.blum@toblux.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).