All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yongpeng Yang <yangyongpeng.storage@gmail.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Yongpeng Yang <yangyongpeng@xiaomi.com>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/3] f2fs: wrap all unusable_blocks_per_sec code in CONFIG_BLK_DEV_ZONED
Date: Mon, 10 Nov 2025 17:34:29 +0800	[thread overview]
Message-ID: <dc863744-49ff-4b7e-96d4-acbf2a07ef7f@kernel.org> (raw)
In-Reply-To: <20251110082223.902207-1-yangyongpeng.storage@gmail.com>

On 11/10/25 16:22, Yongpeng Yang wrote:
> From: Yongpeng Yang <yangyongpeng@xiaomi.com>
> 
> The usage of unusable_blocks_per_sec is already wrapped by
> CONFIG_BLK_DEV_ZONED, except for its declaration and the definitions of
> CAP_BLKS_PER_SEC and CAP_SEGS_PER_SEC. This patch ensures that all code
> related to unusable_blocks_per_sec is properly wrapped under the
> CONFIG_BLK_DEV_ZONED option.
> 
> Signed-off-by: Yongpeng Yang <yangyongpeng@xiaomi.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
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-10  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10  8:22 [f2fs-dev] [PATCH v2 1/3] f2fs: wrap all unusable_blocks_per_sec code in CONFIG_BLK_DEV_ZONED Yongpeng Yang
2025-11-10  8:22 ` [f2fs-dev] [PATCH v2 2/3] f2fs: add a sysfs entry to show max open zones Yongpeng Yang
2025-11-10  9:40   ` Chao Yu via Linux-f2fs-devel
2025-11-10  8:22 ` [f2fs-dev] [PATCH v2 3/3] f2fs: fix handling of zoned block devices with max_open_zones == 0 Yongpeng Yang
2025-11-10  9:47   ` Chao Yu via Linux-f2fs-devel
2025-11-12 21:42   ` Jaegeuk Kim via Linux-f2fs-devel
2025-11-14  0:51     ` Chao Yu via Linux-f2fs-devel
2025-11-14  7:37       ` Yongpeng Yang
2025-11-15 11:36         ` Chao Yu via Linux-f2fs-devel
2025-11-16 16:31           ` Yongpeng Yang
2025-11-16 18:10             ` Yongpeng Yang
2025-11-17  2:03             ` Chao Yu via Linux-f2fs-devel
2025-11-10  9:34 ` Chao Yu via Linux-f2fs-devel [this message]
2025-11-24 18:50 ` [f2fs-dev] [PATCH v2 1/3] f2fs: wrap all unusable_blocks_per_sec code in CONFIG_BLK_DEV_ZONED 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=dc863744-49ff-4b7e-96d4-acbf2a07ef7f@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=yangyongpeng.storage@gmail.com \
    --cc=yangyongpeng@xiaomi.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.