From: David Howells <dhowells@redhat.com>
To: Anna Schumaker <Anna.Schumaker@Netapp.com>
Cc: dhowells@redhat.com, mszeredi@redhat.com,
viro@zeniv.linux.org.uk, jlayton@redhat.com,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]
Date: Thu, 11 May 2017 20:24:32 +0100 [thread overview]
Message-ID: <9616.1494530672@warthog.procyon.org.uk> (raw)
In-Reply-To: <68231d1a-9902-ce3d-73e3-6e74754832e4@Netapp.com>
Anna Schumaker <Anna.Schumaker@Netapp.com> wrote:
> Is there any way to split the NFS patch into multiple pieces?
Are you okay with a patch or two that add code that is unconnected in that
patch, but connected in a later one?
David
next prev parent reply other threads:[~2017-05-11 19:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 13:59 [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2] David Howells
2017-05-11 13:59 ` [PATCH 01/14] Provide a function to create a NUL-terminated string from unterminated data " David Howells
2017-05-11 14:00 ` [PATCH 02/14] Clean up whitespace in fs/namespace.c " David Howells
2017-05-11 14:00 ` [PATCH 03/14] VFS: Make get_mnt_ns() return the namespace " David Howells
2017-05-11 14:00 ` [PATCH 04/14] VFS: Make get_filesystem() return the affected filesystem " David Howells
2017-05-11 14:00 ` [PATCH 05/14] VFS: Provide empty name qstr " David Howells
2017-05-11 14:00 ` [PATCH 06/14] VFS: Introduce a superblock configuration context " David Howells
2017-05-11 14:00 ` [PATCH 07/14] Implement fsopen() to prepare for a mount " David Howells
2017-05-11 14:01 ` [PATCH 08/14] Implement fsmount() to effect a pre-configured " David Howells
2017-05-11 14:01 ` [PATCH 09/14] Sample program for driving fsopen/fsmount " David Howells
2017-05-11 14:01 ` [PATCH 10/14] procfs: Move proc_fill_super() to fs/proc/root.c " David Howells
2017-05-11 14:01 ` [PATCH 11/14] proc: Add superblock config support to procfs " David Howells
2017-05-11 14:01 ` [PATCH 12/14] NFS: Add mount context support. " David Howells
2017-05-11 14:01 ` [PATCH 13/14] Support legacy filesystems " David Howells
2017-05-11 14:01 ` [PATCH 14/14] Add commands to create or update a superblock " David Howells
2017-05-11 17:26 ` [RFC][PATCH 00/14] VFS: Introduce superblock configuration context " Anna Schumaker
2017-05-11 19:24 ` David Howells [this message]
2017-05-12 13:55 ` Anna Schumaker
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=9616.1494530672@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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).