From: Li GuiFu via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Gao Xiang <hsiangkao@aol.com>, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] erofs-utils: more sanity check for buffer allocation optimization
Date: Sun, 28 Feb 2021 21:21:59 +0800 [thread overview]
Message-ID: <901a00d5-c181-79d9-66ff-fff6146a317e@aliyun.com> (raw)
In-Reply-To: <20210214153549.2454-2-hsiangkao@aol.com>
On 2021/2/14 23:35, Gao Xiang via Linux-erofs wrote:
> From: Gao Xiang <hsiangkao@aol.com>
>
> In case that new buffer allocation optimization logic is
> potentially broken.
>
> Signed-off-by: Gao Xiang <hsiangkao@aol.com>
> ---
It looks good
Reviewed-by: Li Guifu <bluce.lee@aliyun.com>
Thanks,
prev parent reply other threads:[~2021-02-28 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210214153549.2454-1-hsiangkao.ref@aol.com>
2021-02-14 15:35 ` [PATCH v2 1/2] erofs-utils: don't reuse full mapped buffer blocks Gao Xiang via Linux-erofs
2021-02-14 15:35 ` [PATCH v2 2/2] erofs-utils: more sanity check for buffer allocation optimization Gao Xiang via Linux-erofs
2021-02-28 13:21 ` Li GuiFu via Linux-erofs [this message]
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=901a00d5-c181-79d9-66ff-fff6146a317e@aliyun.com \
--to=linux-erofs@lists.ozlabs.org \
--cc=bluce.lee@aliyun.com \
--cc=hsiangkao@aol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).