mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux ocfs2 <ocfs2-devel@lists.linux.dev>
Cc: Jonathan Corbet <corbet@lwn.net>, Mark Fasheh <mark@fasheh.com>,
	Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH] Documentation: ocfs2: Properly reindent filecheck operations list
Date: Thu, 28 Aug 2025 09:10:58 +0800	[thread overview]
Message-ID: <e0af0cee-9477-4179-ade5-7df879e22f02@linux.alibaba.com> (raw)
In-Reply-To: <20250826024756.16073-1-bagasdotme@gmail.com>



On 2025/8/26 10:47, Bagas Sanjaya wrote:
> Some of texts in filecheck operations list are indented out of the list.
> In particular, the third operation is shown not as the third list
> item but rather as a separate paragraph.
> 
> Reindent the list so that gets properly rendered as such.
> 
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
>  .../filesystems/ocfs2-online-filecheck.rst    | 20 +++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/Documentation/filesystems/ocfs2-online-filecheck.rst b/Documentation/filesystems/ocfs2-online-filecheck.rst
> index 2257bb53edc1b1..9e8449416e0bee 100644
> --- a/Documentation/filesystems/ocfs2-online-filecheck.rst
> +++ b/Documentation/filesystems/ocfs2-online-filecheck.rst
> @@ -58,33 +58,33 @@ inode, fixing inode and setting the size of result record history.
>      # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/check
>      # cat /sys/fs/ocfs2/<devname>/filecheck/check
>  
> -The output is like this::
> +   The output is like this::
>  
>      INO		DONE	ERROR
>      39502		1	GENERATION
>  
> -    <INO> lists the inode numbers.
> -    <DONE> indicates whether the operation has been finished.
> -    <ERROR> says what kind of errors was found. For the detailed error numbers,
> -    please refer to the file linux/fs/ocfs2/filecheck.h.
> +   <INO> lists the inode numbers.
> +   <DONE> indicates whether the operation has been finished.
> +   <ERROR> says what kind of errors was found. For the detailed error numbers,
> +   please refer to the file linux/fs/ocfs2/filecheck.h.
>  
>  2. If you determine to fix this inode, do::
>  
>      # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/fix
>      # cat /sys/fs/ocfs2/<devname>/filecheck/fix
>  
> -The output is like this:::
> +   The output is like this::
>  
>      INO		DONE	ERROR
>      39502		1	SUCCESS
>  
> -This time, the <ERROR> column indicates whether this fix is successful or not.
> +   This time, the <ERROR> column indicates whether this fix is successful or not.
>  
>  3. The record cache is used to store the history of check/fix results. It's
> -default size is 10, and can be adjust between the range of 10 ~ 100. You can
> -adjust the size like this::
> +   default size is 10, and can be adjust between the range of 10 ~ 100. You can
> +   adjust the size like this::
>  
> -  # echo "<size>" > /sys/fs/ocfs2/<devname>/filecheck/set
> +    # echo "<size>" > /sys/fs/ocfs2/<devname>/filecheck/set
>  
>  Fixing stuff
>  ============
> 
> base-commit: ee9a6691935490dc39605882b41b9452844d5e4e


  reply	other threads:[~2025-08-28  1:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  2:47 Bagas Sanjaya
2025-08-28  1:10 ` Joseph Qi [this message]
2025-08-29 21:51 ` Jonathan Corbet

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=e0af0cee-9477-4179-ade5-7df879e22f02@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jlbec@evilplan.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    /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®