From: Ilya Dryomov <idryomov@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Xiubo Li <xiubli@redhat.com>, Jeff Layton <jlayton@kernel.org>,
ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ceph: Convert ceph_writepages_start() to use folios a little more
Date: Sat, 24 Jun 2023 09:41:47 +0200 [thread overview]
Message-ID: <CAOi1vP8sLbtM2R07Hu-G-+uQxN5pCZEEwF-qa2foeMb6exwAYQ@mail.gmail.com> (raw)
In-Reply-To: <ZJEgN2J5zLqsuehk@casper.infradead.org>
On Tue, Jun 20, 2023 at 5:42 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Jun 07, 2023 at 08:31:46AM +0800, Xiubo Li wrote:
> >
> > On 6/7/23 02:19, Matthew Wilcox wrote:
> > > On Tue, Jun 06, 2023 at 01:37:46PM +0800, Xiubo Li wrote:
> > > > This Looks good to me.
> > > >
> > > > BTW, could you rebase this to the 'testing' branch ? This will introduce a
> > > Umm, which testing branch is that? It applies cleanly to next-20230606
> > > which is generally where I work, since it's a bit unreasonable for me
> > > to keep track of every filesystem development tree.
> >
> > Here https://github.com/ceph/ceph-client/commits/testing.
>
> Are the fscrypt patches planned for 6.5? Because they really should
> have been in -next a few weeks ago if they are.
Hi Matthew,
No, they are currently targeted for 6.6.
Thanks,
Ilya
prev parent reply other threads:[~2023-06-24 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 16:54 [PATCH] ceph: Convert ceph_writepages_start() to use folios a little more Matthew Wilcox (Oracle)
2023-06-06 5:37 ` Xiubo Li
2023-06-06 18:19 ` Matthew Wilcox
2023-06-07 0:31 ` Xiubo Li
2023-06-20 3:42 ` Matthew Wilcox
2023-06-24 7:41 ` Ilya Dryomov [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=CAOi1vP8sLbtM2R07Hu-G-+uQxN5pCZEEwF-qa2foeMb6exwAYQ@mail.gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xiubli@redhat.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).