From: Jeff Layton <jlayton@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
ceph-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] ceph: Uninline the data on a file opened for writing
Date: Mon, 17 Jan 2022 09:30:09 -0500 [thread overview]
Message-ID: <b9ad354b5282dbfce6c64287e14132ace83d91ef.camel@kernel.org> (raw)
In-Reply-To: <2768911.1642429628@warthog.procyon.org.uk>
On Mon, 2022-01-17 at 14:27 +0000, David Howells wrote:
> Jeff Layton <jlayton@kernel.org> wrote:
>
> > That would be nicer, I think. If you do that though, then patch #3
> > probably needs to come first in the series...
>
> Seems reasonable. Could you do that, or do you want me to have a go at it?
>
Do you mind doing it? I can take a stab at it, but it may be a while
before I can get to it.
Thanks,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2022-01-17 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 12:44 [PATCH 1/3] ceph: Uninline the data on a file opened for writing David Howells
2022-01-17 12:44 ` [PATCH 2/3] ceph: Remove some other inline-setting bits David Howells
2022-01-17 12:44 ` [PATCH 3/3] ceph: Make ceph_netfs_issue_op() handle inlined data (untested) David Howells
2022-01-17 13:47 ` [PATCH 1/3] ceph: Uninline the data on a file opened for writing Matthew Wilcox
2022-01-17 14:11 ` Jeff Layton
2022-01-17 14:27 ` David Howells
2022-01-17 14:30 ` Jeff Layton [this message]
2022-01-17 15:24 ` David Howells
2022-01-17 15:45 ` Jeff Layton
2022-01-17 15:57 ` David Howells
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=b9ad354b5282dbfce6c64287e14132ace83d91ef.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@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).