From: Trond Myklebust <trondmy@hammerspace.com>
To: "aglo@umich.edu" <aglo@umich.edu>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"neilb@suse.com" <neilb@suse.com>
Subject: Re: multipath patches
Date: Fri, 12 Jul 2019 19:09:07 +0000 [thread overview]
Message-ID: <88a507b1974d9a8f9c2afa17f246feab31d6ee09.camel@hammerspace.com> (raw)
In-Reply-To: <CAN-5tyEiJUS_HJPCaO+A272f-orQqeRQo-7zF8qMcieZt=410Q@mail.gmail.com>
On Fri, 2019-07-12 at 14:02 -0400, Olga Kornievskaia wrote:
>
> Hi Trond,
>
> With the latest patch in the testing branch, I can mount.
Excellent! Thanks for your patience and for testing.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2019-07-12 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 19:06 multipath patches Olga Kornievskaia
2019-07-11 19:29 ` Trond Myklebust
2019-07-11 20:33 ` Olga Kornievskaia
2019-07-11 21:13 ` Trond Myklebust
2019-07-12 16:39 ` Olga Kornievskaia
2019-07-12 17:18 ` Trond Myklebust
2019-07-12 18:02 ` Olga Kornievskaia
2019-07-12 19:09 ` Trond Myklebust [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=88a507b1974d9a8f9c2afa17f246feab31d6ee09.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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).