From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Yue Hu <zbestahu@gmail.com>
Cc: zbestahu@163.com, huyue2@yulong.com, xiang@kernel.org,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: correct the only tail-end data comment in __allocate_inode_bh_data()
Date: Wed, 16 Jun 2021 20:54:26 +0800 [thread overview]
Message-ID: <YMn0giPxXljefwK7@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <20210616080112.941-1-zbestahu@gmail.com>
On Wed, Jun 16, 2021 at 04:01:12PM +0800, Yue Hu wrote:
> From: Yue Hu <huyue2@yulong.com>
>
> nblocks = 0 means only tail-end data which may be inlined or not(ENOSPC).
> Acturally, we also observed this non-inline tail-end data case.
>
> Signed-off-by: Yue Hu <huyue2@yulong.com>
Reviewed-by: Gao Xiang <xiang@kernel.org>
Thanks,
Gao Xiang
prev parent reply other threads:[~2021-06-16 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 8:01 [PATCH] erofs-utils: correct the only tail-end data comment in __allocate_inode_bh_data() Yue Hu
2021-06-16 12:54 ` Gao Xiang [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=YMn0giPxXljefwK7@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=huyue2@yulong.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@kernel.org \
--cc=zbestahu@163.com \
--cc=zbestahu@gmail.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).