All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, daehojeong@google.com,
	corbet@lwn.net, frank.li@vivo.com, jaegeuk@kernel.org,
	yuanye.ma20@gmail.com
Subject: Re: [f2fs-dev] [PATCH 0/6] f2fs: documentation formatting cleanup and improvements
Date: Tue, 02 Sep 2025 20:20:09 +0000	[thread overview]
Message-ID: <175684440975.425353.8499498509115681029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820043432.22509-1-bagasdotme@gmail.com>

Hello:

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

On Wed, 20 Aug 2025 11:34:26 +0700 you wrote:
> Hi,
> 
> Here are documentation formatting cleanup for f2fs. This also includes
> docs retitle at the end of series ([6/6]) as a bonus.
> 
> This series is based on docs-next tree.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/6] Documentation: f2fs: Separate errors mode subtable
    https://git.kernel.org/jaegeuk/f2fs/c/4bc6bf7b8830
  - [f2fs-dev,2/6] Documentation: f2fs: Format compression level subtable
    https://git.kernel.org/jaegeuk/f2fs/c/f23044152af2
  - [f2fs-dev,3/6] Documentation: f2fs: Span write hint table section rows
    https://git.kernel.org/jaegeuk/f2fs/c/f9c97e496293
  - [f2fs-dev,4/6] Documentation: f2fs: Wrap snippets in literal code blocks
    https://git.kernel.org/jaegeuk/f2fs/c/f4f36fffd872
  - [f2fs-dev,5/6] Documentation: f2fs: Indent compression_mode option list
    https://git.kernel.org/jaegeuk/f2fs/c/e78223268878
  - [f2fs-dev,6/6] Documentation: f2fs: Reword title
    https://git.kernel.org/jaegeuk/f2fs/c/62242ac51061

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: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: daehojeong@google.com, corbet@lwn.net, frank.li@vivo.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	yuanye.ma20@gmail.com
Subject: Re: [f2fs-dev] [PATCH 0/6] f2fs: documentation formatting cleanup and improvements
Date: Tue, 02 Sep 2025 20:20:09 +0000	[thread overview]
Message-ID: <175684440975.425353.8499498509115681029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820043432.22509-1-bagasdotme@gmail.com>

Hello:

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

On Wed, 20 Aug 2025 11:34:26 +0700 you wrote:
> Hi,
> 
> Here are documentation formatting cleanup for f2fs. This also includes
> docs retitle at the end of series ([6/6]) as a bonus.
> 
> This series is based on docs-next tree.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/6] Documentation: f2fs: Separate errors mode subtable
    https://git.kernel.org/jaegeuk/f2fs/c/4bc6bf7b8830
  - [f2fs-dev,2/6] Documentation: f2fs: Format compression level subtable
    https://git.kernel.org/jaegeuk/f2fs/c/f23044152af2
  - [f2fs-dev,3/6] Documentation: f2fs: Span write hint table section rows
    https://git.kernel.org/jaegeuk/f2fs/c/f9c97e496293
  - [f2fs-dev,4/6] Documentation: f2fs: Wrap snippets in literal code blocks
    https://git.kernel.org/jaegeuk/f2fs/c/f4f36fffd872
  - [f2fs-dev,5/6] Documentation: f2fs: Indent compression_mode option list
    https://git.kernel.org/jaegeuk/f2fs/c/e78223268878
  - [f2fs-dev,6/6] Documentation: f2fs: Reword title
    https://git.kernel.org/jaegeuk/f2fs/c/62242ac51061

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-09-02 20:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20  4:34 [PATCH 0/6] f2fs: documentation formatting cleanup and improvements Bagas Sanjaya
2025-08-20  4:34 ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 1/6] Documentation: f2fs: Separate errors mode subtable Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 2/6] Documentation: f2fs: Format compression level subtable Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 3/6] Documentation: f2fs: Span write hint table section rows Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 4/6] Documentation: f2fs: Wrap snippets in literal code blocks Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 5/6] Documentation: f2fs: Indent compression_mode option list Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-20  4:34 ` [PATCH 6/6] Documentation: f2fs: Reword title Bagas Sanjaya
2025-08-20  4:34   ` [f2fs-dev] " Bagas Sanjaya
2025-08-25  1:59 ` [PATCH 0/6] f2fs: documentation formatting cleanup and improvements Chao Yu
2025-08-25  1:59   ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-08-29 22:31 ` Jonathan Corbet
2025-08-29 22:31   ` [f2fs-dev] " Jonathan Corbet
2025-08-30 23:56   ` Jaegeuk Kim
2025-08-30 23:56     ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2025-08-31 20:12     ` Jonathan Corbet
2025-08-31 20:12       ` [f2fs-dev] " Jonathan Corbet
2025-09-02 20:20 ` patchwork-bot+f2fs [this message]
2025-09-02 20:20   ` patchwork-bot+f2fs--- 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=175684440975.425353.8499498509115681029.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=daehojeong@google.com \
    --cc=frank.li@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuanye.ma20@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.