From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/8] erofs: drop z_erofs_page_mark_eio()
Date: Fri, 18 Aug 2023 11:20:37 +0800 [thread overview]
Message-ID: <20230818112037.000027ef.zbestahu@gmail.com> (raw)
In-Reply-To: <20230817082813.81180-5-hsiangkao@linux.alibaba.com>
On Thu, 17 Aug 2023 16:28:10 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> It can be folded into z_erofs_onlinepage_endio() to simplify the code.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Yue Hu <huyue2@coolpad.com>
next prev parent reply other threads:[~2023-08-18 3:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 8:28 [PATCH 1/8] erofs: simplify z_erofs_read_fragment() Gao Xiang
2023-08-17 8:28 ` [PATCH 2/8] erofs: avoid obsolete {collector,collection} terms Gao Xiang
2023-08-18 2:25 ` Yue Hu
2023-08-23 14:58 ` Chao Yu
2023-08-17 8:28 ` [PATCH 3/8] erofs: move preparation logic into z_erofs_pcluster_begin() Gao Xiang
2023-08-18 2:42 ` Yue Hu
2023-08-23 15:05 ` Chao Yu
2023-08-23 15:22 ` Gao Xiang
2023-08-17 8:28 ` [PATCH 4/8] erofs: tidy up z_erofs_do_read_page() Gao Xiang
2023-08-18 3:12 ` Yue Hu
2023-08-23 15:09 ` Chao Yu
2023-08-17 8:28 ` [PATCH 5/8] erofs: drop z_erofs_page_mark_eio() Gao Xiang
2023-08-18 3:20 ` Yue Hu [this message]
2023-08-23 15:19 ` Chao Yu
2023-08-17 8:28 ` [PATCH 6/8] erofs: get rid of fe->backmost for cache decompression Gao Xiang
2023-08-18 5:51 ` Yue Hu
2023-08-18 7:48 ` Gao Xiang
2023-08-18 8:02 ` Yue Hu
2023-08-23 15:19 ` Chao Yu
2023-08-17 8:28 ` [PATCH 7/8] erofs: adapt folios for z_erofs_readahead() Gao Xiang
2023-08-23 15:22 ` Chao Yu
2023-08-17 8:28 ` [PATCH 8/8] erofs: adapt folios for z_erofs_read_folio() Gao Xiang
2023-08-17 8:39 ` [PATCH v2 " Gao Xiang
2023-08-23 15:23 ` [PATCH " Chao Yu
2023-08-18 2:18 ` [PATCH 1/8] erofs: simplify z_erofs_read_fragment() Yue Hu
2023-08-23 14:56 ` Chao Yu
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=20230818112037.000027ef.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--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