All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, Barry Song <baohua@kernel.org>,
	Nanzhe Zhao <nzzhao@126.com>, Juan Yescas <jyescas@google.com>,
	Dev Jain <Dev.Jain@arm.com>,
	linux-kernel@vger.kernel.org,
	David Hildenbrand <David.Hildenbrand@arm.com>,
	Bo Zhang <zhangbo56@xiaomi.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	Ryan Roberts <Ryan.Roberts@arm.com>,
	Pengfei Li <lipengfei28@xiaomi.com>
Subject: Re: [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages
Date: Mon, 31 Aug 2026 15:46:21 +0800	[thread overview]
Message-ID: <404d2f2b-c8b6-43de-a6e4-9e4989ae5d44@kernel.org> (raw)
In-Reply-To: <20260826082641.2007658-11-zhaonanzhe@xiaomi.com>

On 8/26/26 16:26, Nanzhe Zhao wrote:
> A large folio can be partial truncated and stays in folio mapping, we
> need to clear the subrange dirty bits and uptodate bits that the partial
> truncate covers. If this partial truncate happens to clear the last
> subrange dirty bits, then cancel the whole folio dirty state.
> 
> Also add a guard in f2fs_write_single_data_folio() so a large folio
> subpage whose disk block was already truncated (NULL_ADDR) is skipped
> 
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
>   fs/f2fs/data.c | 74 +++++++++++++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 73 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 59b07b83b216..15774e8e8795 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -2693,6 +2693,34 @@ static void f2fs_ffs_mark_subrange_uptodate(struct folio *folio, size_t offset,
>   		folio_mark_uptodate(folio);
>   }
>   
> +static void ffs_clear_subrange_uptodate(struct folio *folio,
> +					size_t offset, size_t len)
> +{
> +	struct f2fs_folio_state *ffs;
> +	unsigned int nr_subpages, start, end;
> +	unsigned long flags;
> +
> +	f2fs_bug_on(F2FS_F_SB(folio), offset + len > folio_size(folio));
> +
> +	if (!f2fs_folio_has_ffs(folio)) {
> +		if (folio_test_uptodate(folio))
> +			folio_clear_uptodate(folio);
> +		return;
> +	}
> +
> +	ffs = (struct f2fs_folio_state *)folio->private;
> +	nr_subpages = folio_nr_pages(folio);
> +	start = offset >> PAGE_SHIFT;
> +	end = (offset + len + PAGE_SIZE - 1) >> PAGE_SHIFT;
> +	end = min(end, nr_subpages);
> +
> +	spin_lock_irqsave(&ffs->state_lock, flags);
> +	bitmap_clear(ffs->state, start, end - start);
> +	spin_unlock_irqrestore(&ffs->state_lock, flags);
> +	if (folio_test_uptodate(folio))
> +		folio_clear_uptodate(folio);
> +}
> +
>   bool f2fs_ffs_test_blk_dirty(const struct folio *folio, pgoff_t index)
>   {
>   	struct f2fs_folio_state *ffs;
> @@ -3599,6 +3627,21 @@ static int f2fs_write_single_data_folio(struct folio *folio, int *submitted,
>   
>   		fio.old_blkaddr = dn.data_blkaddr;
>   
> +		/* This page is already truncated */
> +		if (fio.old_blkaddr == NULL_ADDR) {
> +			ffs_clear_subrange_uptodate(folio,
> +					i << PAGE_SHIFT, PAGE_SIZE);
> +			folio_clear_f2fs_gcing(folio);
> +			f2fs_put_dnode(&dn);
> +			if (f2fs_folio_has_ffs(folio)) {
> +				struct f2fs_folio_state *ffs =
> +					(struct f2fs_folio_state *)folio->private;
> +
> +				atomic_dec(&ffs->write_pages_pending);
> +			}
> +			continue;
> +		}
> +
>   got_it:
>   		if (__is_valid_data_blkaddr(fio.old_blkaddr) &&
>   		    !f2fs_is_valid_blkaddr(sbi, fio.old_blkaddr,
> @@ -5075,8 +5118,37 @@ void f2fs_invalidate_folio(struct folio *folio, size_t offset, size_t length)
>   	struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
>   
>   	if (inode->i_ino >= F2FS_ROOT_INO(sbi) &&
> -				(offset || length != folio_size(folio)))
> +				(offset || length != folio_size(folio))) {
> +		size_t clear_start = ALIGN(offset, PAGE_SIZE);

round_up(offset, PAGE_SIZE) will be more efficient?

> +		size_t clear_end = round_down(offset + length, PAGE_SIZE);
> +		size_t clear_length = 0;
> +
> +		/*
> +		 * If the truncated range falls within a single subpage, no
> +		 * subpage state needs to be cleared.
> +		 */
> +		if (clear_start < clear_end && f2fs_folio_has_ffs(folio)) {

How about cleaning up to avoid long line w/

if (clear_start >= clear_end || !f2fs_folio_has_ffs(folio))
	return;

> +			bool dirty;
> +
> +			clear_length = clear_end - clear_start;
> +			dirty = f2fs_ffs_clear_subrange_dirty(folio,
> +							clear_start, clear_length);
> +			ffs_clear_subrange_uptodate(folio, clear_start,
> +							clear_length);
> +
> +			/*
> +			 * If the truncated subrange happens to clear the
> +			 * remaining dirty bitmap of the whole folio, cancel
> +			 * the folio-level dirty state.
> +			 */
> +			if (!dirty && folio_test_dirty(folio)) {
> +				inode_dec_dirty_pages(inode);
> +				f2fs_remove_dirty_inode(inode);
> +				folio_cancel_dirty(folio);
> +			}
> +		}
>   		return;
> +	}
>   
>   	if (folio_test_dirty(folio)) {
>   		if (inode->i_ino == F2FS_META_INO(sbi)) {


WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Barry Song <baohua@kernel.org>, Juan Yescas <jyescas@google.com>,
	Dev Jain <Dev.Jain@arm.com>,
	linux-kernel@vger.kernel.org,
	David Hildenbrand <David.Hildenbrand@arm.com>,
	Bo Zhang <zhangbo56@xiaomi.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	Nanzhe Zhao <nzzhao@126.com>, Pengfei Li <lipengfei28@xiaomi.com>,
	Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [f2fs-dev] [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages
Date: Mon, 31 Aug 2026 15:46:21 +0800	[thread overview]
Message-ID: <404d2f2b-c8b6-43de-a6e4-9e4989ae5d44@kernel.org> (raw)
In-Reply-To: <20260826082641.2007658-11-zhaonanzhe@xiaomi.com>

On 8/26/26 16:26, Nanzhe Zhao wrote:
> A large folio can be partial truncated and stays in folio mapping, we
> need to clear the subrange dirty bits and uptodate bits that the partial
> truncate covers. If this partial truncate happens to clear the last
> subrange dirty bits, then cancel the whole folio dirty state.
> 
> Also add a guard in f2fs_write_single_data_folio() so a large folio
> subpage whose disk block was already truncated (NULL_ADDR) is skipped
> 
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
>   fs/f2fs/data.c | 74 +++++++++++++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 73 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 59b07b83b216..15774e8e8795 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -2693,6 +2693,34 @@ static void f2fs_ffs_mark_subrange_uptodate(struct folio *folio, size_t offset,
>   		folio_mark_uptodate(folio);
>   }
>   
> +static void ffs_clear_subrange_uptodate(struct folio *folio,
> +					size_t offset, size_t len)
> +{
> +	struct f2fs_folio_state *ffs;
> +	unsigned int nr_subpages, start, end;
> +	unsigned long flags;
> +
> +	f2fs_bug_on(F2FS_F_SB(folio), offset + len > folio_size(folio));
> +
> +	if (!f2fs_folio_has_ffs(folio)) {
> +		if (folio_test_uptodate(folio))
> +			folio_clear_uptodate(folio);
> +		return;
> +	}
> +
> +	ffs = (struct f2fs_folio_state *)folio->private;
> +	nr_subpages = folio_nr_pages(folio);
> +	start = offset >> PAGE_SHIFT;
> +	end = (offset + len + PAGE_SIZE - 1) >> PAGE_SHIFT;
> +	end = min(end, nr_subpages);
> +
> +	spin_lock_irqsave(&ffs->state_lock, flags);
> +	bitmap_clear(ffs->state, start, end - start);
> +	spin_unlock_irqrestore(&ffs->state_lock, flags);
> +	if (folio_test_uptodate(folio))
> +		folio_clear_uptodate(folio);
> +}
> +
>   bool f2fs_ffs_test_blk_dirty(const struct folio *folio, pgoff_t index)
>   {
>   	struct f2fs_folio_state *ffs;
> @@ -3599,6 +3627,21 @@ static int f2fs_write_single_data_folio(struct folio *folio, int *submitted,
>   
>   		fio.old_blkaddr = dn.data_blkaddr;
>   
> +		/* This page is already truncated */
> +		if (fio.old_blkaddr == NULL_ADDR) {
> +			ffs_clear_subrange_uptodate(folio,
> +					i << PAGE_SHIFT, PAGE_SIZE);
> +			folio_clear_f2fs_gcing(folio);
> +			f2fs_put_dnode(&dn);
> +			if (f2fs_folio_has_ffs(folio)) {
> +				struct f2fs_folio_state *ffs =
> +					(struct f2fs_folio_state *)folio->private;
> +
> +				atomic_dec(&ffs->write_pages_pending);
> +			}
> +			continue;
> +		}
> +
>   got_it:
>   		if (__is_valid_data_blkaddr(fio.old_blkaddr) &&
>   		    !f2fs_is_valid_blkaddr(sbi, fio.old_blkaddr,
> @@ -5075,8 +5118,37 @@ void f2fs_invalidate_folio(struct folio *folio, size_t offset, size_t length)
>   	struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
>   
>   	if (inode->i_ino >= F2FS_ROOT_INO(sbi) &&
> -				(offset || length != folio_size(folio)))
> +				(offset || length != folio_size(folio))) {
> +		size_t clear_start = ALIGN(offset, PAGE_SIZE);

round_up(offset, PAGE_SIZE) will be more efficient?

> +		size_t clear_end = round_down(offset + length, PAGE_SIZE);
> +		size_t clear_length = 0;
> +
> +		/*
> +		 * If the truncated range falls within a single subpage, no
> +		 * subpage state needs to be cleared.
> +		 */
> +		if (clear_start < clear_end && f2fs_folio_has_ffs(folio)) {

How about cleaning up to avoid long line w/

if (clear_start >= clear_end || !f2fs_folio_has_ffs(folio))
	return;

> +			bool dirty;
> +
> +			clear_length = clear_end - clear_start;
> +			dirty = f2fs_ffs_clear_subrange_dirty(folio,
> +							clear_start, clear_length);
> +			ffs_clear_subrange_uptodate(folio, clear_start,
> +							clear_length);
> +
> +			/*
> +			 * If the truncated subrange happens to clear the
> +			 * remaining dirty bitmap of the whole folio, cancel
> +			 * the folio-level dirty state.
> +			 */
> +			if (!dirty && folio_test_dirty(folio)) {
> +				inode_dec_dirty_pages(inode);
> +				f2fs_remove_dirty_inode(inode);
> +				folio_cancel_dirty(folio);
> +			}
> +		}
>   		return;
> +	}
>   
>   	if (folio_test_dirty(folio)) {
>   		if (inode->i_ino == F2FS_META_INO(sbi)) {



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

  reply	other threads:[~2026-08-31  7:46 UTC|newest]

Thread overview: 136+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  8:26 [f2fs-dev] [PATCH 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26 ` Nanzhe Zhao
2026-08-26  8:26 ` [f2fs-dev] [PATCH 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27  6:57   ` Chao Yu
2026-08-27  6:57     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-27 20:51     ` Daeho Jeong
2026-08-27 20:51       ` Daeho Jeong
2026-09-04  3:44       ` Daeho Jeong
2026-09-04  3:44         ` Daeho Jeong
2026-09-07  6:49       ` Nanzhe Zhao
2026-09-07  6:49         ` Nanzhe Zhao
2026-09-07  9:31       ` Nanzhe Zhao
2026-09-07  9:31         ` Nanzhe Zhao
2026-09-09 20:25         ` Daeho Jeong
2026-09-09 20:25           ` Daeho Jeong
2026-09-08  3:41       ` Nanzhe Zhao
2026-09-08  3:41         ` Nanzhe Zhao
2026-08-26  8:26 ` [f2fs-dev] [PATCH 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27  7:16   ` Chao Yu
2026-08-27  7:16     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-27 21:06     ` Daeho Jeong
2026-08-27 21:06       ` Daeho Jeong
2026-08-26  8:26 ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27  8:56   ` Chao Yu
2026-08-27  8:56     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-27 21:13     ` Daeho Jeong
2026-08-27 21:13       ` Daeho Jeong
2026-09-07  3:51     ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes Nanzhe Zhao
2026-09-07  3:51       ` Nanzhe Zhao
2026-09-07  6:59       ` Chao Yu
2026-09-07  6:59         ` Chao Yu via Linux-f2fs-devel
2026-09-07 11:58     ` Nanzhe Zhao
2026-09-07 11:58       ` Nanzhe Zhao
2026-09-07 13:03     ` Nanzhe Zhao
2026-09-07 13:03       ` Nanzhe Zhao
2026-09-09  8:41       ` Chao Yu
2026-09-09  8:41         ` Chao Yu via Linux-f2fs-devel
2026-09-09 20:40     ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Daeho Jeong
2026-09-09 20:40       ` Daeho Jeong
2026-09-10 10:33       ` Nanzhe Zhao
2026-09-10 10:33         ` Nanzhe Zhao via Linux-f2fs-devel
2026-08-31  3:04   ` Chao Yu
2026-08-31  3:04     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26  8:26 ` [f2fs-dev] [PATCH 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27  9:24   ` Chao Yu
2026-08-27  9:24     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26  8:26 ` [f2fs-dev] [PATCH 05/14] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27 11:17   ` Chao Yu
2026-08-27 11:17     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-27 22:39     ` Daeho Jeong
2026-08-27 22:39       ` Daeho Jeong
2026-09-04  4:04       ` Daeho Jeong
2026-09-04  4:04         ` Daeho Jeong
2026-09-04  4:07         ` Daeho Jeong
2026-09-04  4:07           ` Daeho Jeong
2026-09-07  3:57         ` Nanzhe Zhao
2026-09-07  3:57           ` Nanzhe Zhao
2026-09-09 21:03           ` Daeho Jeong
2026-09-09 21:03             ` Daeho Jeong
2026-09-07 10:12       ` Nanzhe Zhao
2026-09-07 10:12         ` Nanzhe Zhao
2026-09-09 21:08         ` Daeho Jeong
2026-09-09 21:08           ` Daeho Jeong
2026-09-07  3:51     ` Nanzhe Zhao
2026-09-07  3:51       ` Nanzhe Zhao
2026-09-07  6:59       ` Chao Yu
2026-09-07  6:59         ` Chao Yu via Linux-f2fs-devel
2026-08-26  8:26 ` [f2fs-dev] [PATCH 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-27 12:36   ` Chao Yu
2026-08-27 12:36     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-28 17:18     ` Daeho Jeong
2026-08-28 17:18       ` Daeho Jeong
2026-09-07  7:34     ` Nanzhe Zhao
2026-09-07  7:34       ` Nanzhe Zhao
2026-09-09  7:34       ` Chao Yu
2026-09-09  7:34         ` Chao Yu via Linux-f2fs-devel
2026-09-09 21:22         ` Daeho Jeong
2026-09-09 21:22           ` Daeho Jeong
2026-08-26  8:26 ` [f2fs-dev] [PATCH 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-28 17:20   ` [f2fs-dev] " Daeho Jeong
2026-08-28 17:20     ` Daeho Jeong
2026-09-07 11:45     ` Nanzhe Zhao
2026-09-07 11:45       ` Nanzhe Zhao
2026-09-09 19:33       ` Daeho Jeong
2026-09-09 19:33         ` Daeho Jeong
2026-08-31  3:14   ` Chao Yu
2026-08-31  3:14     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26  8:26 ` [f2fs-dev] [PATCH 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-31  4:21   ` Chao Yu
2026-08-31  4:21     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26  8:26 ` [f2fs-dev] [PATCH 09/14] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-26  8:26 ` [f2fs-dev] [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-08-26  8:26   ` Nanzhe Zhao
2026-08-31  7:46   ` Chao Yu [this message]
2026-08-31  7:46     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [PATCH 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-08-26 13:09   ` [f2fs-dev] " Nanzhe Zhao via Linux-f2fs-devel
2026-08-31  7:56   ` Chao Yu
2026-08-31  7:56     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [PATCH 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-08-26 13:09   ` [f2fs-dev] " Nanzhe Zhao via Linux-f2fs-devel
2026-08-31  8:19   ` Chao Yu
2026-08-31  8:19     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-09-07  9:57     ` Nanzhe Zhao
2026-09-07  9:57       ` Nanzhe Zhao
2026-09-07 10:24       ` Chao Yu
2026-09-07 10:24         ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [PATCH 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-08-26 13:09   ` [f2fs-dev] " Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:44   ` Daeho Jeong
2026-08-28 17:44     ` Daeho Jeong
2026-09-07  6:33     ` Nanzhe Zhao
2026-09-07  6:33       ` Nanzhe Zhao
2026-09-09 19:23       ` Daeho Jeong
2026-09-09 19:23         ` Daeho Jeong
2026-08-31  8:31   ` Chao Yu
2026-08-31  8:31     ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-09-07 11:14     ` Nanzhe Zhao
2026-09-07 11:14       ` Nanzhe Zhao
2026-08-26 13:09 ` [PATCH 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-08-26 13:09   ` [f2fs-dev] " Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:52   ` Daeho Jeong
2026-08-28 17:52     ` Daeho Jeong
2026-09-07  3:45     ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-07  3:45       ` Nanzhe Zhao
2026-08-31  8:46   ` Chao Yu
2026-08-31  8:46     ` [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=404d2f2b-c8b6-43de-a6e4-9e4989ae5d44@kernel.org \
    --to=chao@kernel.org \
    --cc=David.Hildenbrand@arm.com \
    --cc=Dev.Jain@arm.com \
    --cc=Ryan.Roberts@arm.com \
    --cc=baohua@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jyescas@google.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipengfei28@xiaomi.com \
    --cc=nzzhao@126.com \
    --cc=zhangbo56@xiaomi.com \
    --cc=zhaonanzhe@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.