From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org,
Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH next] Documentation: filesystems: tftp: fix code blocks
Date: Tue, 13 Sep 2022 10:08:37 +0200 [thread overview]
Message-ID: <20220913080837.GG6477@pengutronix.de> (raw)
In-Reply-To: <20220912085047.84819-1-antonynpavlov@gmail.com>
On Mon, Sep 12, 2022 at 11:50:47AM +0300, Antony Pavlov wrote:
> The patch fixes these sphinx errors:
>
> Documentation/filesystems/tftp.rst:44: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 3 supplied.
> Documentation/filesystems/tftp.rst:53: ERROR: Error in "code-block" directive:
> maximum 1 argument(s) allowed, 4 supplied.
>
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> ---
> Documentation/filesystems/tftp.rst | 2 ++
> 1 file changed, 2 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/Documentation/filesystems/tftp.rst b/Documentation/filesystems/tftp.rst
> index 8929213d3c4..e88ad3dd4c8 100644
> --- a/Documentation/filesystems/tftp.rst
> +++ b/Documentation/filesystems/tftp.rst
> @@ -42,6 +42,7 @@ the opposite effect. Performance depends on:
> 100 Mb/s) it had to be reduced to
>
> .. code-block:: console
> +
> global tftp.windowsize=26
>
> for example.
> @@ -51,6 +52,7 @@ the opposite effect. Performance depends on:
> example, the `fec-imx` driver reserves place for
>
> .. code-block:: c
> +
> #define FEC_RBD_NUM 64
>
> packets before they are dropped
> --
> 2.37.2
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-09-13 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:50 Antony Pavlov
2022-09-13 8:08 ` Sascha Hauer [this message]
2022-09-13 9:54 ` Antony Pavlov
2022-09-13 11:05 ` Sascha Hauer
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=20220913080837.GG6477@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=enrico.scholz@sigma-chemnitz.de \
/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