From: Carlos Maiolino <cmaiolino@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix Sphinx documentation warning
Date: Mon, 9 Dec 2019 15:49:06 +0100 [thread overview]
Message-ID: <20191209144906.u3hllhe5ekkqsvva@orion> (raw)
In-Reply-To: <bd3c7d7e-2859-06b0-a209-7d19f7c2e79f@infradead.org>
On Sun, Dec 08, 2019 at 08:14:36PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix Sphinx documentation format warning by not indenting so much.
>
> Documentation/admin-guide/xfs.rst:257: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Darrick J. Wong <darrick.wong@oracle.com>
> Cc: linux-xfs@vger.kernel.org
> ---
> Documentation/admin-guide/xfs.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Looks good, you can add:
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
>
> --- linux-next-20191209.orig/Documentation/admin-guide/xfs.rst
> +++ linux-next-20191209/Documentation/admin-guide/xfs.rst
> @@ -253,7 +253,7 @@ The following sysctls are available for
> pool.
>
> fs.xfs.speculative_prealloc_lifetime
> - (Units: seconds Min: 1 Default: 300 Max: 86400)
> + (Units: seconds Min: 1 Default: 300 Max: 86400)
> The interval at which the background scanning for inodes
> with unused speculative preallocation runs. The scan
> removes unused preallocation from clean inodes and releases
>
--
Carlos
prev parent reply other threads:[~2019-12-09 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 4:14 [PATCH] xfs: fix Sphinx documentation warning Randy Dunlap
2019-12-09 14:49 ` Carlos Maiolino [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=20191209144906.u3hllhe5ekkqsvva@orion \
--to=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).