From: Chao Yu <chao@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>, xiang@kernel.org
Cc: huyue2@coolpad.com, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] erofs: modify the error message when prepare_ondemand_read failed
Date: Sun, 28 Apr 2024 14:23:08 +0800 [thread overview]
Message-ID: <e8b33c6d-2d9c-461d-ae47-bbd74d7f203b@kernel.org> (raw)
In-Reply-To: <20240424084247.759432-1-lihongbo22@huawei.com>
On 2024/4/24 16:42, Hongbo Li wrote:
> When prepare_ondemand_read failed, wrong error message is printed.
> The prepare_read is also implemented in cachefiles, so we amend it.
>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-04-28 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 8:42 [PATCH -next] erofs: modify the error message when prepare_ondemand_read failed Hongbo Li via Linux-erofs
2024-04-24 11:21 ` Jingbo Xu
2024-04-28 6:23 ` Chao Yu [this message]
[not found] <20240424023945.420828-1-lihongbo22@huawei.com>
2024-04-24 3:29 ` Gao Xiang
2024-04-24 8:44 ` Hongbo Li via Linux-erofs
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=e8b33c6d-2d9c-461d-ae47-bbd74d7f203b@kernel.org \
--to=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).