From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Huang Jianan <huangjianan@oppo.com>,
Chia-Wei Wang <chiawei_wang@aspeedtech.com>,
Arnd Bergmann <arnd@arndb.de>, Amit Kucheria <amitk@kernel.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation/ABI: sysfs-fs-erofs: Fix Sphinx errors
Date: Fri, 25 Mar 2022 12:33:53 +0800 [thread overview]
Message-ID: <Yj1GMaQN/W+kpT6e@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <20220324165918.22005-4-hdegoede@redhat.com>
On Thu, Mar 24, 2022 at 05:59:18PM +0100, Hans de Goede wrote:
> Fix the following warnings from "make htmldocs":
>
> Documentation/ABI/testing/sysfs-fs-erofs:10:
> ERROR: Unexpected indentation.
> WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Thanks!
Acked-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Thanks,
Gao Xiang
> ---
> Documentation/ABI/testing/sysfs-fs-erofs | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-fs-erofs b/Documentation/ABI/testing/sysfs-fs-erofs
> index 05482374a741..bb4681a01811 100644
> --- a/Documentation/ABI/testing/sysfs-fs-erofs
> +++ b/Documentation/ABI/testing/sysfs-fs-erofs
> @@ -9,8 +9,9 @@ Description: Shows all enabled kernel features.
> What: /sys/fs/erofs/<disk>/sync_decompress
> Date: November 2021
> Contact: "Huang Jianan" <huangjianan@oppo.com>
> -Description: Control strategy of sync decompression
> +Description: Control strategy of sync decompression:
> +
> - 0 (default, auto): enable for readpage, and enable for
> - readahead on atomic contexts only,
> + readahead on atomic contexts only.
> - 1 (force on): enable for readpage and readahead.
> - 2 (force off): disable for all situations.
> --
> 2.35.1
prev parent reply other threads:[~2022-03-25 4:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 16:59 [PATCH 0/3] Documentation/ABI/testing: Sphinx warning fixes Hans de Goede
2022-03-24 16:59 ` [PATCH 1/3] Documentation/ABI: sysfs-driver-aspeed-uart-routing: Fix sphinx warning Hans de Goede
2022-03-25 10:43 ` Hans de Goede
2022-03-24 16:59 ` [PATCH 2/3] Documentation/ABI: sysfs-class-thermal: Fix Sphinx warning Hans de Goede
2022-03-24 16:59 ` [PATCH 3/3] Documentation/ABI: sysfs-fs-erofs: Fix Sphinx errors Hans de Goede
2022-03-25 4:33 ` Gao Xiang [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=Yj1GMaQN/W+kpT6e@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=amitk@kernel.org \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=chiawei_wang@aspeedtech.com \
--cc=daniel.lezcano@linaro.org \
--cc=hdegoede@redhat.com \
--cc=huangjianan@oppo.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfr@canb.auug.org.au \
/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).