From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: dhowells@redhat.com,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"cmaiolino@redhat.com" <cmaiolino@redhat.com>,
"carmark.dlut@gmail.com" <carmark.dlut@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
"dwysocha@redhat.com" <dwysocha@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: [PATCH 0/5] cachefiles, nfs: Fixes
Date: Sun, 10 May 2020 21:35:43 +0100 [thread overview]
Message-ID: <1787830.1589142943@warthog.procyon.org.uk> (raw)
In-Reply-To: <d4efead1d6dba67f5c862a8d00ca88dd3c45dd34.camel@hammerspace.com>
Trond Myklebust <trondmy@hammerspace.com> wrote:
> I can pull this branch, and send it together with the NFS client
> bugfixes for 5.7-rc5.
Thanks!
David
next prev parent reply other threads:[~2020-05-10 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 22:16 [PATCH 0/5] cachefiles, nfs: Fixes David Howells
2020-05-08 22:16 ` [PATCH 1/5] cachefiles: Fix corruption of the return value in cachefiles_read_or_alloc_pages() David Howells
2020-05-08 22:17 ` [PATCH 2/5] NFS: Fix fscache super_cookie index_key from changing after umount David Howells
2020-05-08 22:17 ` [PATCH 3/5] NFS: Fix fscache super_cookie allocation David Howells
2020-05-08 22:17 ` [PATCH 4/5] NFSv4: Fix fscache cookie aux_data to ensure change_attr is included David Howells
2020-05-08 22:17 ` [PATCH 5/5] cachefiles: Fix race between read_waiter and read_copier involving op->to_do David Howells
2020-05-10 13:39 ` [PATCH 0/5] cachefiles, nfs: Fixes Trond Myklebust
2020-05-10 20:35 ` David Howells [this message]
2020-05-11 22:38 ` NeilBrown
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=1787830.1589142943@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=carmark.dlut@gmail.com \
--cc=cmaiolino@redhat.com \
--cc=dwysocha@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@hammerspace.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