linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] SQUASHME: pnfs-submit: Use LAYOUT_NFSV4_1_FILES instead of LAYOUT_NFSV4_FILES
Date: Tue, 25 May 2010 09:55:02 +0300	[thread overview]
Message-ID: <4BFB7446.7000608@panasas.com> (raw)
In-Reply-To: <1274722623-11078-1-git-send-email-Ricardo.Labiaga@netapp.com>

On May. 24, 2010, 20:37 +0300, Ricardo Labiaga <Ricardo.Labiaga@netapp.com> wrote:
> So that we can be consistent with the spec definitions.
> 
> Signed-off-by: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>

Committed at pnfs-all-2.6.34-2010-05-25

Thanks!

Benny

> ---
>  fs/nfs/nfs4filelayout.c    |    4 ++--
>  fs/nfs/nfs4filelayoutdev.c |    2 +-
>  include/linux/nfs4.h       |    2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
> index 9d1274d..d39315a 100644
> --- a/fs/nfs/nfs4filelayout.c
> +++ b/fs/nfs/nfs4filelayout.c
> @@ -766,8 +766,8 @@ struct layoutdriver_policy_operations filelayout_policy_operations = {
>  };
>  
>  struct pnfs_layoutdriver_type filelayout_type = {
> -	.id = LAYOUT_NFSV4_FILES,
> -	.name = "LAYOUT_NFSV4_FILES",
> +	.id = LAYOUT_NFSV4_1_FILES,
> +	.name = "LAYOUT_NFSV4_1_FILES",
>  	.ld_io_ops = &filelayout_io_operations,
>  	.ld_policy_ops = &filelayout_policy_operations,
>  };
> diff --git a/fs/nfs/nfs4filelayoutdev.c b/fs/nfs/nfs4filelayoutdev.c
> index 462f6de..b540679 100644
> --- a/fs/nfs/nfs4filelayoutdev.c
> +++ b/fs/nfs/nfs4filelayoutdev.c
> @@ -510,7 +510,7 @@ get_device_info(struct inode *inode, struct pnfs_deviceid *dev_id)
>  		goto out_free;
>  
>  	memcpy(&pdev->dev_id, dev_id, NFS4_PNFS_DEVICEID4_SIZE);
> -	pdev->layout_type = LAYOUT_NFSV4_FILES;
> +	pdev->layout_type = LAYOUT_NFSV4_1_FILES;
>  	pdev->pages = pages;
>  	pdev->pgbase = 0;
>  	pdev->pglen = PAGE_SIZE * max_pages;
> diff --git a/include/linux/nfs4.h b/include/linux/nfs4.h
> index 1730e86..219e6b4 100644
> --- a/include/linux/nfs4.h
> +++ b/include/linux/nfs4.h
> @@ -565,7 +565,7 @@ enum state_protect_how4 {
>  };
>  
>  enum pnfs_layouttype {
> -	LAYOUT_NFSV4_FILES  = 1,
> +	LAYOUT_NFSV4_1_FILES  = 1,
>  	LAYOUT_OSD2_OBJECTS = 2,
>  	LAYOUT_BLOCK_VOLUME = 3,
>  };

      parent reply	other threads:[~2010-05-25  6:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 17:37 [PATCH 1/2] SQUASHME: pnfs-submit: Use LAYOUT_NFSV4_1_FILES instead of LAYOUT_NFSV4_FILES Ricardo Labiaga
2010-05-24 17:37 ` [PATCH 2/2] pnfs-submit: Dynamically load the nfslayoutdriver Ricardo Labiaga
2010-05-25  6:55   ` Benny Halevy
2010-05-25  5:56 ` [PATCH 1/3] SQUASHME: pnfsd: dlm: fixup LAYOUT_NFSV4_1_FILES Benny Halevy
2010-05-25  5:56 ` [PATCH 2/3] SQUASHME: pnfsd-lexp: " Benny Halevy
2010-05-25  5:56 ` [PATCH 3/3] SQUASHME: spnfs: " Benny Halevy
2010-05-25 11:20   ` Boaz Harrosh
2010-05-25 14:44     ` Benny Halevy
2010-05-25  6:55 ` Benny Halevy [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=4BFB7446.7000608@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=Ricardo.Labiaga@netapp.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 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).