From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>,
linux-erofs@lists.ozlabs.org, Liu Bo <bo.liu@linux.alibaba.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Yue Hu <huyue2@yulong.com>
Subject: Re: [PATCH v2 2/5] erofs: use meta buffers for inode operations
Date: Tue, 4 Jan 2022 15:57:02 +0800 [thread overview]
Message-ID: <2d841b67-27d0-df57-fff0-fa8fb2c4175c@kernel.org> (raw)
In-Reply-To: <20220102040017.51352-3-hsiangkao@linux.alibaba.com>
On 2022/1/2 12:00, Gao Xiang wrote:
> Get rid of old erofs_get_meta_page() within inode operations by
> using on-stack meta buffers in order to prepare subpage and folio
> features.
>
> Reviewed-by: Yue Hu <huyue2@yulong.com>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2022-01-04 7:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 4:00 [PATCH v2 0/5] erofs: get rid of erofs_get_meta_page() Gao Xiang
2022-01-02 4:00 ` [PATCH v2 1/5] erofs: introduce meta buffer operations Gao Xiang
2022-01-02 7:48 ` Liu Bo
2022-01-04 7:54 ` Chao Yu
2022-01-04 9:05 ` Gao Xiang
2022-01-02 4:00 ` [PATCH v2 2/5] erofs: use meta buffers for inode operations Gao Xiang
2022-01-02 7:48 ` Liu Bo
2022-01-04 7:57 ` Chao Yu [this message]
2022-01-02 4:00 ` [PATCH v2 3/5] erofs: use meta buffers for super operations Gao Xiang
2022-01-02 7:23 ` Liu Bo
2022-01-02 8:06 ` Gao Xiang
2022-01-02 8:13 ` [PATCH v3 " Gao Xiang
2022-01-02 8:15 ` Liu Bo
2022-01-04 8:02 ` Chao Yu
2022-01-02 4:00 ` [PATCH v2 4/5] erofs: use meta buffers for xattr operations Gao Xiang
2022-01-02 7:48 ` Liu Bo
2022-01-04 8:07 ` Chao Yu
2022-01-02 4:00 ` [PATCH v2 5/5] erofs: use meta buffers for zmap operations Gao Xiang
2022-01-02 7:47 ` Liu Bo
2022-01-04 8:15 ` Chao Yu
2022-01-04 9:02 ` Gao Xiang
2022-01-04 12:44 ` 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=2d841b67-27d0-df57-fff0-fa8fb2c4175c@kernel.org \
--to=chao@kernel.org \
--cc=bo.liu@linux.alibaba.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@yulong.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
Powered by JetHome