From: Patrick Donnelly <pdonnell@redhat.com>
To: Venky Shankar <vshankar@redhat.com>
Cc: Jeff Layton <jlayton@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
lhenriques@suse.de, Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] ceph: new mount device syntax
Date: Fri, 2 Jul 2021 11:05:46 -0700 [thread overview]
Message-ID: <CA+2bHPbxR94_Bc-C5Ly7HQvwQPsoBr-j+fomGkTcBM5=8aS=0g@mail.gmail.com> (raw)
In-Reply-To: <20210702064821.148063-1-vshankar@redhat.com>
On Thu, Jul 1, 2021 at 11:48 PM Venky Shankar <vshankar@redhat.com> wrote:
> Also note that the userspace mount helper tool is backward
> compatible. I.e., the mount helper will fallback to using
> old syntax after trying to mount with the new syntax.
The kernel is also backwards compatible too, right?
--
Patrick Donnelly, Ph.D.
He / Him / His
Principal Software Engineer
Red Hat Sunnyvale, CA
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
next prev parent reply other threads:[~2021-07-02 18:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 6:48 [PATCH v2 0/4] ceph: new mount device syntax Venky Shankar
2021-07-02 6:48 ` [PATCH v2 1/4] ceph: new device mount syntax Venky Shankar
2021-07-02 10:38 ` Luis Henriques
2021-07-02 11:05 ` Venky Shankar
2021-07-06 18:41 ` Jeff Layton
2021-07-02 6:48 ` [PATCH v2 2/4] ceph: validate cluster FSID for new device syntax Venky Shankar
2021-07-02 10:44 ` Luis Henriques
2021-07-02 10:48 ` Luis Henriques
2021-07-02 11:10 ` Venky Shankar
2021-07-02 13:49 ` Luis Henriques
2021-07-02 14:57 ` Venky Shankar
2021-07-06 18:35 ` Jeff Layton
2021-07-07 5:05 ` Venky Shankar
2021-07-02 6:48 ` [PATCH v2 3/4] ceph: record updated mon_addr on remount Venky Shankar
2021-07-02 6:48 ` [PATCH v2 4/4] doc: document new CephFS mount device syntax Venky Shankar
2021-07-02 18:08 ` Patrick Donnelly
2021-07-05 4:39 ` Venky Shankar
2021-07-06 18:25 ` Jeff Layton
2021-07-02 18:05 ` Patrick Donnelly [this message]
2021-07-05 4:36 ` [PATCH v2 0/4] ceph: new " Venky Shankar
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='CA+2bHPbxR94_Bc-C5Ly7HQvwQPsoBr-j+fomGkTcBM5=8aS=0g@mail.gmail.com' \
--to=pdonnell@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@redhat.com \
--cc=lhenriques@suse.de \
--cc=vshankar@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).