From: Anna Schumaker <Anna.Schumaker@Netapp.com>
To: David Howells <dhowells@redhat.com>
Cc: <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: Fri, 12 May 2017 09:55:24 -0400 [thread overview]
Message-ID: <5610bd4e-b0a4-79d5-a90e-54cb9e63299f@Netapp.com> (raw)
In-Reply-To: <9616.1494530672@warthog.procyon.org.uk>
On 05/11/2017 03:24 PM, David Howells wrote:
> 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?
Yes, I'm okay with that. Thanks for working on this!
Anna
>
> David
>
prev parent reply other threads:[~2017-05-12 13:55 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
2017-05-12 13:55 ` Anna Schumaker [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=5610bd4e-b0a4-79d5-a90e-54cb9e63299f@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=dhowells@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.