All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/5] NFSD: some bugfixes and updates
Date: Mon, 10 Aug 2015 17:22:16 -0400	[thread overview]
Message-ID: <20150810212216.GF10455@fieldses.org> (raw)
In-Reply-To: <55BA2B46.90204@gmail.com>

On Thu, Jul 30, 2015 at 09:48:54PM +0800, Kinglong Mee wrote:
> The first three are bugfixes, the last two are updates for EXCLUSIVE4_1.

These all look good to me, thanks, applying.--b.

> 
> Kinglong Mee (5):
>   NFSD: Store parent's stat in a sperate value
>   NFSD: Fix a encode bug of FS_LAYOUT_TYPES and LAYOUT_TYPES
>   NFSD: SUPPATTR_EXCLCREAT must be encoded before SECURITY_LABEL.
>   NFSD: Set the attributes used to store the verifier for EXCLUSIVE4_1
>   NFSD: Return word2 bitmask if setting security label in OPEN/CREATE
> 
>  fs/nfsd/nfs4proc.c |  12 ++--
>  fs/nfsd/nfs4xdr.c  | 158 +++++++++++++++++++++++++++++++++--------------------
>  fs/nfsd/vfs.c      |   6 --
>  fs/nfsd/vfs.h      |   6 ++
>  4 files changed, 112 insertions(+), 70 deletions(-)
> 
> -- 
> 2.4.3

      parent reply	other threads:[~2015-08-10 21:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 13:48 [PATCH 0/5] NFSD: some bugfixes and updates Kinglong Mee
2015-07-30 13:51 ` [PATCH 1/5] NFSD: Store parent's stat in a sperate value Kinglong Mee
2015-07-30 13:52 ` [PATCH 2/5] nfsd: Fix a encode bug of FS_LAYOUT_TYPES and LAYOUT_TYPES Kinglong Mee
2015-07-30 15:48   ` Christoph Hellwig
2015-07-30 13:54 ` [PATCH 3/5] nfsd: SUPPATTR_EXCLCREAT must be encoded before SECURITY_LABEL Kinglong Mee
2015-07-30 13:55 ` [PATCH 4/5] NFSD: Set the attributes used to store the verifier for EXCLUSIVE4_1 Kinglong Mee
2015-07-30 13:55 ` [PATCH 5/5] NFSD: Return word2 bitmask if setting security label in OPEN/CREATE Kinglong Mee
2015-08-10 21:22 ` J. Bruce Fields [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=20150810212216.GF10455@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kinglongmee@gmail.com \
    --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 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.