From: Damien Le Moal <dlemoal@kernel.org>
To: Soham Metha <sohammetha01@gmail.com>, linux-doc@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, hch@lst.de
Subject: Re: [PATCH v2 2/9] docs: zoned_loop: fixed spelling mistakes in documentation
Date: Wed, 13 Aug 2025 09:34:31 +0900 [thread overview]
Message-ID: <25bd83bd-6b39-48cd-b31b-dd6f1df00f94@kernel.org> (raw)
In-Reply-To: <20250812202940.70560-1-sohammetha01@gmail.com>
On 8/13/25 05:29, Soham Metha wrote:
> 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>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2025-08-13 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 20:29 [PATCH v2 2/9] docs: zoned_loop: fixed spelling mistakes in documentation Soham Metha
2025-08-13 0:34 ` Damien Le Moal [this message]
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=25bd83bd-6b39-48cd-b31b-dd6f1df00f94@kernel.org \
--to=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=skhan@linuxfoundation.org \
--cc=sohammetha01@gmail.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;
as well as URLs for NNTP newsgroup(s).