From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: 田子晨 <tianzichen@kuaishou.com>
Cc: "jefflexu@linux.alibaba.com" <jefflexu@linux.alibaba.com>,
"chao@kernel.org" <chao@kernel.org>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"gerry@linux.alibaba.com" <gerry@linux.alibaba.com>,
"joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>,
"linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"luodaowen.backend@bytedance.com"
<luodaowen.backend@bytedance.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"willy@infradead.org" <willy@infradead.org>,
"xiang@kernel.org" <xiang@kernel.org>
Subject: Re: [PATCH v5 00/22] fscache, erofs: fscache-based on-demand read semantics
Date: Wed, 23 Mar 2022 12:45:11 +0100 [thread overview]
Message-ID: <YjsIR886wCKosNNu@kroah.com> (raw)
In-Reply-To: <B6EA31D4-877C-450E-BF89-2879044B9EAD@kuaishou.com>
On Wed, Mar 23, 2022 at 08:38:07AM +0000, 田子晨 wrote:
> This solution looks good, and we’ re also interested in it , please accelerate its progress so we can use it.
Please test the patches and provide your feedback on it (i.e.
"Reviewed-by:" and the like.)
thanks,
greg k-h
next parent reply other threads:[~2022-03-23 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B6EA31D4-877C-450E-BF89-2879044B9EAD@kuaishou.com>
2022-03-23 11:45 ` gregkh [this message]
2022-03-16 13:17 [PATCH v5 00/22] fscache,erofs: fscache-based on-demand read semantics Jeffle Xu
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=YjsIR886wCKosNNu@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chao@kernel.org \
--cc=dhowells@redhat.com \
--cc=gerry@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luodaowen.backend@bytedance.com \
--cc=tianzichen@kuaishou.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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