From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: deprecate io_bits
Date: Tue, 20 Feb 2024 15:03:50 +0800 [thread overview]
Message-ID: <4965a052-5918-4b5a-ac00-b5e33c0d9c7b@kernel.org> (raw)
In-Reply-To: <20240207005105.3744811-1-jaegeuk@kernel.org>
On 2024/2/7 8:51, Jaegeuk Kim wrote:
> Let's deprecate an unused io_bits feature to save CPU cycles and memory.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-02-20 7:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 0:51 Jaegeuk Kim
2024-02-07 0:51 ` [PATCH 2/3] f2fs: use BLKS_PER_SEG, BLKS_PER_SEC, and SEGS_PER_SEC Jaegeuk Kim
2024-02-07 23:51 ` [f2fs-dev] " Daeho Jeong
2024-02-12 18:10 ` [PATCH 2/3 v2] " Jaegeuk Kim
2024-02-20 7:30 ` [f2fs-dev] " Chao Yu
2024-02-20 20:33 ` Jaegeuk Kim
2024-02-21 1:04 ` Chao Yu
2024-02-20 20:39 ` [PATCH 2/3 v3] " Jaegeuk Kim
2024-02-21 1:30 ` [f2fs-dev] " Chao Yu
2024-02-21 1:54 ` Jaegeuk Kim
2024-02-21 2:17 ` Chao Yu
2024-02-07 0:51 ` [PATCH 3/3] f2fs: kill zone-capacity support Jaegeuk Kim
2024-02-07 2:42 ` Jaegeuk Kim
2024-02-07 22:27 ` [f2fs-dev] " Daeho Jeong
2024-02-07 23:29 ` [PATCH 3/3 v2] " Jaegeuk Kim
2024-02-07 23:51 ` [f2fs-dev] " Daeho Jeong
2024-02-20 9:48 ` Chao Yu
2024-02-20 19:01 ` Jaegeuk Kim
2024-02-21 8:14 ` Juhyung Park
2024-02-21 17:27 ` Jaegeuk Kim
2024-02-22 14:33 ` Matias Bjørling
2024-02-23 17:38 ` Jaegeuk Kim
2024-02-08 0:11 ` [f2fs-dev] [PATCH 1/3] f2fs: deprecate io_bits Daeho Jeong
2024-02-20 7:03 ` Chao Yu [this message]
2024-02-21 18:10 ` 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=4965a052-5918-4b5a-ac00-b5e33c0d9c7b@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®