From: Soham Metha <sohammetha01@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, dlemoal@kernel.org, hch@lst.de,
Soham Metha <sohammetha01@gmail.com>
Subject: [PATCH v2 2/9] docs: zoned_loop: fixed spelling mistakes in documentation
Date: Wed, 13 Aug 2025 01:59:40 +0530 [thread overview]
Message-ID: <20250812202940.70560-1-sohammetha01@gmail.com> (raw)
found/fixed the following typos
- conventioanl -> conventional
- directoy -> directory
in `Documentation/admin-guide/blockdev/zoned_loop.rst`
Signed-off-by: Soham Metha <sohammetha01@gmail.com>
---
Documentation/admin-guide/blockdev/zoned_loop.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/blockdev/zoned_loop.rst b/Documentation/admin-guide/blockdev/zoned_loop.rst
index 9c7aa3b482f3..2d50d081592b 100644
--- a/Documentation/admin-guide/blockdev/zoned_loop.rst
+++ b/Documentation/admin-guide/blockdev/zoned_loop.rst
@@ -77,9 +77,9 @@ capacity_mb Device total capacity in MiB. This is always rounded up to
zone_size_mb Device zone size in MiB. Default: 256 MiB.
zone_capacity_mb Device zone capacity (must always be equal to or lower than
the zone size. Default: zone size.
-conv_zones Total number of conventioanl zones starting from sector 0.
+conv_zones Total number of conventional zones starting from sector 0.
Default: 8.
-base_dir Path to the base directoy where to create the directory
+base_dir Path to the base directory where to create the directory
containing the zone files of the device.
Default=/var/local/zloop.
The device directory containing the zone files is always
--
2.34.1
next reply other threads:[~2025-08-12 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 20:29 Soham Metha [this message]
2025-08-13 0:34 ` [PATCH v2 2/9] docs: zoned_loop: fixed spelling mistakes in documentation Damien Le Moal
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=20250812202940.70560-1-sohammetha01@gmail.com \
--to=sohammetha01@gmail.com \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.