From: Al Viro <viro@ZenIV.linux.org.uk>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: handle vfs_getattr errors in acl protocol
Date: Sat, 23 Feb 2013 17:41:28 +0000 [thread overview]
Message-ID: <20130223174127.GR4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130222221835.GC30856@fieldses.org>
On Fri, Feb 22, 2013 at 05:18:35PM -0500, J. Bruce Fields wrote:
> > FWIW, I'm going to push the first part of VFS queue later tonight...
>
> OK, I'll wait and see what's in that.
See for-next...
> (And what should I do with the delegation patches?)
Looking through that stuff...
prev parent reply other threads:[~2013-02-23 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:15 [PATCH] nfsd: handle vfs_getattr errors in acl protocol J. Bruce Fields
2013-02-01 18:57 ` Al Viro
2013-02-01 20:13 ` J. Bruce Fields
2013-02-22 21:46 ` J. Bruce Fields
2013-02-22 22:15 ` Al Viro
2013-02-22 22:18 ` J. Bruce Fields
2013-02-23 17:41 ` Al Viro [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=20130223174127.GR4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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).