From: David Howells <dhowells@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: dhowells@redhat.com, Jeff Layton <jlayton@kernel.org>,
Ceph Development <ceph-devel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-cachefs@redhat.com
Subject: Re: [PATCH 0/6] ceph: convert to new netfs read helpers
Date: Mon, 01 Feb 2021 15:25:43 +0000 [thread overview]
Message-ID: <4171610.1612193143@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAOi1vP_7dfuKgQxFpyeUDMJBGm=cnQSvYHDnU=6YPTzbB9+d6w@mail.gmail.com>
Ilya Dryomov <idryomov@gmail.com> wrote:
> > David has a fscache-netfs-lib branch that has all of the infrastructure
> > changes. See:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-netfs-lib
>
> I saw that, but AFAICS it hasn't been declared public (as in suitable
> for other people to base their work on, with the promise that history
> won't get rewritten.
My intention to avoid modifying it further, except for extra fix patches
stacked on the end if necessary, as I want to try to avoid jinxing it from
getting pulled in the next merge window.
> It is branched off of what looks like a random snapshot of Linus' tree
> instead of a release point, etc.
Yeah, sorry about that. I took what was current linus/master at the time I
cut the branch with the intention of trying to get it into linux-next before
-rc5 was tagged (ie. >3 weeks before the merge window), but including the
X.509 crash fix.
David
prev parent reply other threads:[~2021-02-01 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 13:40 [PATCH 0/6] ceph: convert to new netfs read helpers Jeff Layton
2021-01-26 13:40 ` [PATCH 1/6] ceph: disable old fscache readpage handling Jeff Layton
2021-01-26 13:40 ` [PATCH 2/6] ceph: rework PageFsCache handling Jeff Layton
2021-01-26 13:41 ` [PATCH 3/6] ceph: fix fscache invalidation Jeff Layton
2021-01-26 13:41 ` [PATCH 4/6] ceph: convert readpage to fscache read helper Jeff Layton
2021-01-26 13:41 ` [PATCH 5/6] ceph: plug write_begin into " Jeff Layton
2021-01-26 13:41 ` [PATCH 6/6] ceph: convert ceph_readpages to ceph_readahead Jeff Layton
2021-01-27 22:50 ` [PATCH 0/6] ceph: convert to new netfs read helpers Ilya Dryomov
2021-01-28 12:52 ` Jeff Layton
2021-01-28 20:48 ` Ilya Dryomov
2021-02-01 15:25 ` David Howells [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=4171610.1612193143@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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 NNTP newsgroup(s).