All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Masaharu Noguchi <nogunix@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, akiyks@gmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, bagasdotme@gmail.com
Subject: Re: [f2fs-dev] [PATCH v5] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build
Date: Mon, 24 Nov 2025 18:50:13 +0000	[thread overview]
Message-ID: <176401021399.42009.9871104675547871251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251117122754.297742-1-nogunix@gmail.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 17 Nov 2025 21:27:54 +0900 you wrote:
> Sphinx's LaTeX builder fails when converting the nested ASCII tables in
> f2fs.rst, producing the following error:
> 
>   "Markup is unsupported in LaTeX: longtable does not support nesting a table."
> 
> Wrap the affected ASCII tables in literal code blocks to force Sphinx to
> render them verbatim. This prevents nested longtables and fixes the PDF
> build failure on Sphinx 8.2.x.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v5] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build
    https://git.kernel.org/jaegeuk/f2fs/c/c0ee17208345

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Masaharu Noguchi <nogunix@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, akiyks@gmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, bagasdotme@gmail.com,
	jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH v5] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build
Date: Mon, 24 Nov 2025 18:50:13 +0000	[thread overview]
Message-ID: <176401021399.42009.9871104675547871251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251117122754.297742-1-nogunix@gmail.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 17 Nov 2025 21:27:54 +0900 you wrote:
> Sphinx's LaTeX builder fails when converting the nested ASCII tables in
> f2fs.rst, producing the following error:
> 
>   "Markup is unsupported in LaTeX: longtable does not support nesting a table."
> 
> Wrap the affected ASCII tables in literal code blocks to force Sphinx to
> render them verbatim. This prevents nested longtables and fixes the PDF
> build failure on Sphinx 8.2.x.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v5] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build
    https://git.kernel.org/jaegeuk/f2fs/c/c0ee17208345

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2025-11-24 18:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 12:27 [PATCH v5] docs: f2fs: wrap ASCII tables in literal blocks to fix LaTeX build Masaharu Noguchi
2025-11-17 12:27 ` [f2fs-dev] " Masaharu Noguchi
2025-11-21 17:48 ` Jonathan Corbet
2025-11-21 17:48   ` [f2fs-dev] " Jonathan Corbet
2025-11-21 17:59   ` Jaegeuk Kim
2025-11-21 17:59     ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-11-21 19:31     ` Jonathan Corbet
2025-11-21 19:31       ` [f2fs-dev] " Jonathan Corbet
2025-11-24 18:50 ` patchwork-bot+f2fs [this message]
2025-11-24 18:50   ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-25  1:06 ` Chao Yu
2025-11-25  1:06   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel

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=176401021399.42009.9871104675547871251.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.