From: Jonathan Corbet <corbet@lwn.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux F2FS <linux-f2fs-devel@lists.sourceforge.net>,
Chao Yu <chao@kernel.org>, Daeho Jeong <daehojeong@google.com>,
Yuanye Ma <yuanye.ma20@gmail.com>, Yangtao Li <frank.li@vivo.com>
Subject: Re: [PATCH 0/6] f2fs: documentation formatting cleanup and improvements
Date: Sun, 31 Aug 2025 14:12:15 -0600 [thread overview]
Message-ID: <874itn1c9s.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aLOPq_zLap9PuMrW@google.com>
Jaegeuk Kim <jaegeuk@kernel.org> writes:
> On 08/29, Jonathan Corbet wrote:
>> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>>
>> > 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.
>> >
>> > Enjoy!
>> >
>> > Bagas Sanjaya (6):
>> > Documentation: f2fs: Separate errors mode subtable
>> > Documentation: f2fs: Format compression level subtable
>> > Documentation: f2fs: Span write hint table section rows
>> > Documentation: f2fs: Wrap snippets in literal code blocks
>> > Documentation: f2fs: Indent compression_mode option list
>> > Documentation: f2fs: Reword title
>> >
>> > Documentation/filesystems/f2fs.rst | 88 +++++++++++++++++-------------
>> > 1 file changed, 50 insertions(+), 38 deletions(-)
>>
>> Jaegeuk, are you going to pick this up, or would you like me to?
>
> Hi, I applied them in the f2fs tree, if you don't mind.
Not at all - thanks for letting me know!
jon
next prev parent reply other threads:[~2025-08-31 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 4:34 Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 1/6] Documentation: f2fs: Separate errors mode subtable Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 2/6] Documentation: f2fs: Format compression level subtable 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 ` [PATCH 4/6] Documentation: f2fs: Wrap snippets in literal code blocks Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 5/6] Documentation: f2fs: Indent compression_mode option list Bagas Sanjaya
2025-08-20 4:34 ` [PATCH 6/6] Documentation: f2fs: Reword title Bagas Sanjaya
2025-08-25 1:59 ` [PATCH 0/6] f2fs: documentation formatting cleanup and improvements Chao Yu
2025-08-29 22:31 ` Jonathan Corbet
2025-08-30 23:56 ` Jaegeuk Kim
2025-08-31 20:12 ` Jonathan Corbet [this message]
2025-09-02 20:20 ` [f2fs-dev] " patchwork-bot+f2fs
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=874itn1c9s.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=chao@kernel.org \
--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 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®