From: Shuah Khan <skhan@linuxfoundation.org>
To: Eslam Khafagy <eslam.medhat1993@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] dm-crypt: documentation: fix Unexpected indentation error.
Date: Mon, 12 Aug 2024 03:10:23 -0600 [thread overview]
Message-ID: <f32eea28-9d0c-4315-b9fc-776681e10309@linuxfoundation.org> (raw)
In-Reply-To: <20240810211557.42874-1-eslam.medhat1993@gmail.com>
On 8/10/24 15:15, Eslam Khafagy wrote:
> this fixes indentation error at Documentation/admin-guide/device-mapper/dm-crypt.rst
> when compiling the documentation as per sphinx documentation: Nested lists must be separated
> from the parent list items by blank lines
Include information on how you found this problem. Write change log to say
what is fixed. Check submitting_patches document details on:
"Describe your changes in imperative mood"
You are missing documentation maintainer and others - run get_maintainer.pl
script.
>
> Signed-off-by: Eslam Khafagy <eslam.medhat1993@gmail.com>
> ---
> Documentation/admin-guide/device-mapper/dm-crypt.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/admin-guide/device-mapper/dm-crypt.rst b/Documentation/admin-guide/device-mapper/dm-crypt.rst
> index e625830d335e..dc6ded632b22 100644
> --- a/Documentation/admin-guide/device-mapper/dm-crypt.rst
> +++ b/Documentation/admin-guide/device-mapper/dm-crypt.rst
> @@ -164,6 +164,7 @@ iv_large_sectors
> Module parameters::
> max_read_size
> max_write_size
> +
> Maximum size of read or write requests. When a request larger than this size
> is received, dm-crypt will split the request. The splitting improves
> concurrency (the split requests could be encrypted in parallel by multiple
thanks,
-- Shuah
prev parent reply other threads:[~2024-08-12 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 21:15 Eslam Khafagy
2024-08-12 9:10 ` Shuah Khan [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=f32eea28-9d0c-4315-b9fc-776681e10309@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=eslam.medhat1993@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®