From: Hyunchul Lee <hyc.lee@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Namjae Jeon <linkinjeon@kernel.org>,
linux-fsdevel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] ntfs: repair docum. malformed table
Date: Thu, 26 Feb 2026 14:26:12 +0900 [thread overview]
Message-ID: <aZ_ZdKZ1ZHpCHcH8@hyunchul-PC02> (raw)
In-Reply-To: <20260226020615.495490-1-rdunlap@infradead.org>
On Wed, Feb 25, 2026 at 06:06:15PM -0800, Randy Dunlap wrote:
> Make the top and bottom borders be that same length to
> avoid a documentation build error:
>
> Documentation/filesystems/ntfs.rst:159: ERROR: Malformed table.
> Bottom border or header rule does not match top border.
>
> (top)
> ======================= ===================================================
> (bottom)
> ======================= ==================================================
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Looks good to me. Thanks for the patch, Randy.
Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
> ---
> Cc: Namjae Jeon <linkinjeon@kernel.org>
> Cc: Hyunchul Lee <hyc.lee@gmail.com>
> Cc: linux-fsdevel@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
>
> Documentation/filesystems/ntfs.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20260225.orig/Documentation/filesystems/ntfs.rst
> +++ linux-next-20260225/Documentation/filesystems/ntfs.rst
> @@ -39,7 +39,7 @@ Supported mount options
>
> The NTFS driver supports the following mount options:
>
> -======================= ===================================================
> +======================= ====================================================
> iocharset=name Character set to use for converting between
> the encoding is used for user visible filename and
> 16 bit Unicode characters.
> @@ -156,4 +156,4 @@ windows_names=<BOOL> Refuse creation/
> discard=<BOOL> Issue block device discard for clusters freed on
> file deletion/truncation to inform underlying
> storage.
> -======================= ==================================================
> +======================= ====================================================
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-02-26 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 2:06 [PATCH] ntfs: repair docum. malformed table Randy Dunlap
2026-02-26 5:26 ` Hyunchul Lee [this message]
2026-02-26 9:28 ` Namjae Jeon
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=aZ_ZdKZ1ZHpCHcH8@hyunchul-PC02 \
--to=hyc.lee@gmail.com \
--cc=corbet@lwn.net \
--cc=linkinjeon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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