From: Sumya Hoque <sumyahoque2012@gmail.com>
To: skhan@linuxfoundation.org
Cc: linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org,
Sumya Hoque <sumyahoque2012@gmail.com>
Subject: [PATCH] Documentation:FS:Fix minor typos in filesystems/f2fs.rst
Date: Tue, 18 Feb 2025 21:32:21 +0000 [thread overview]
Message-ID: <20250218213221.557744-1-sumyahoque2012@gmail.com> (raw)
Hello,
Here is a minor fix in Kernel Documents:
filesystems/f2fs.rst : comp_extention --> comp_extension
Signed-off-by: Sumya Hoque <sumyahoque2012@gmail.com>
---
Documentation/filesystems/f2fs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
index fb7d2ee022bc..412b0949143b 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst
@@ -310,7 +310,7 @@ nocompress_extension=%s Support adding specified extension, so that f2fs can di
nocompress extension will be treated as special cases and will not be compressed.
Don't allow use '*' to specifie all file in nocompress extension.
After add nocompress_extension, the priority should be:
- dir_flag < comp_extention,nocompress_extension < comp_file_flag,no_comp_file_flag.
+ dir_flag < comp_extension,nocompress_extension < comp_file_flag,no_comp_file_flag.
See more in compression sections.
compress_chksum Support verifying chksum of raw data in compressed cluster.
--
2.34.1
next reply other threads:[~2025-02-18 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 21:32 Sumya Hoque [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-18 21:30 [PATCH] Documentation:FS:Fix minor typos in filesystems/f2fs.rst Sumya Hoque
2025-02-18 21:21 Sumya Hoque
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=20250218213221.557744-1-sumyahoque2012@gmail.com \
--to=sumyahoque2012@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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