From: Akira Yokosawa <akiyks@gmail.com>
To: Masaharu Noguchi <nogunix@gmail.com>
Cc: corbet@lwn.net, linux-f2fs-devel@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
bagasdotme@gmail.com, jaegeuk@kernel.org, chao@kernel.org
Subject: Re: [PATCH v4] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build
Date: Mon, 17 Nov 2025 11:39:52 +0900 [thread overview]
Message-ID: <ca5ef73b-c394-4c63-b47d-40f2ff61ef42@gmail.com> (raw)
In-Reply-To: <20251116102644.25400-1-nogunix@gmail.com>
On Sun, 16 Nov 2025 19:26:44 +0900, Masaharu Noguchi wrote:
> Sphinx LaTeX builder fails on nested tables in f2fs.rst, producing:
>
> “Markup is unsupported in LaTeX: longtable does not support nesting a table.”
>
> Wrap the affected ASCII tables in literal code blocks so Sphinx renders them
> verbatim. This avoids nested longtables and fixes the LaTeX build on Sphinx 8.2.x.
>
> Changes in v4:
> - Rebased on 62242ac51061
> - Cleaned up Changelog placement (move version history above '---')
This is not what I asked by saying:
These background and change history should go out of the Changelog area.
Changelog ends at '---'. See:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#commentary
> - Verified `make htmldocs` and `make pdfdocs` build fine
>
> Changes in v3:
> - Replace TABs inside ASCII tables with spaces
>
> Changes in v2:
> - Wrap nested ASCII tables in literal blocks and fix missing blank lines
>
> Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
> Signed-off-by: Masaharu Noguchi <nogunix@gmail.com>
>
> Link: https://www.spinics.net/lists/kernel/msg5921848.html
> Link: https://www.spinics.net/lists/kernel/msg5918264.html
> Link: https://www.spinics.net/lists/kernel/msg5875662.html
> ---
> Documentation/filesystems/f2fs.rst | 131 +++++++++++++++--------------
> 1 file changed, 69 insertions(+), 62 deletions(-)
./scripts/checkpatch.pl emits the following:
------------------------------------------------------------------------
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#26:
“Markup is unsupported in LaTeX: longtable does not support nesting a table.”
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 62242ac51061 ("Documentation: f2fs: Reword title")'
#32:
- Rebased on 62242ac51061
WARNING: Use lore.kernel.org archive links when possible - see https://lore.kernel.org/lists.html
#46:
Link: https://www.spinics.net/lists/kernel/msg5921848.html
WARNING: Use lore.kernel.org archive links when possible - see https://lore.kernel.org/lists.html
#47:
Link: https://www.spinics.net/lists/kernel/msg5918264.html
WARNING: Use lore.kernel.org archive links when possible - see https://lore.kernel.org/lists.html
#48:
Link: https://www.spinics.net/lists/kernel/msg5875662.html
------------------------------------------------------------------------
Also, please apply your patch on your own before submitting it and
see the Changelog looks good to you.
Thanks, Akira
prev parent reply other threads:[~2025-11-17 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 10:26 [PATCH v4] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build Masaharu Noguchi
2025-11-17 2:39 ` Akira Yokosawa [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=ca5ef73b-c394-4c63-b47d-40f2ff61ef42@gmail.com \
--to=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nogunix@gmail.com \
/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