linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org, Andy Adamson <andros@netapp.com>
Subject: [PATCH 03/11] SQUASHME pnfs-submit rename pnfs_layout_type 3
Date: Wed, 18 Aug 2010 10:44:10 -0400	[thread overview]
Message-ID: <1282142658-21579-4-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1282142658-21579-3-git-send-email-andros@netapp.com>

From: Andy Adamson <andros@netapp.com>

squash into pnfs_submit: layout segment alloc, reference, destroy

Signed-off-by: Andy Adamson <andros@netapp.com>
---
 fs/nfs/pnfs.c             |    2 +-
 include/linux/nfs4_pnfs.h |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/pnfs.c b/fs/nfs/pnfs.c
index bf86975..98f53c2 100644
--- a/fs/nfs/pnfs.c
+++ b/fs/nfs/pnfs.c
@@ -412,7 +412,7 @@ pnfs_destroy_all_layouts(struct nfs_client *clp)
 }
 
 static inline void
-init_lseg(struct pnfs_layout_type *lo, struct pnfs_layout_segment *lseg)
+init_lseg(struct pnfs_layout_hdr *lo, struct pnfs_layout_segment *lseg)
 {
 	INIT_LIST_HEAD(&lseg->fi_list);
 	kref_init(&lseg->kref);
diff --git a/include/linux/nfs4_pnfs.h b/include/linux/nfs4_pnfs.h
index 59a1a12..89d0e7e 100644
--- a/include/linux/nfs4_pnfs.h
+++ b/include/linux/nfs4_pnfs.h
@@ -137,7 +137,7 @@ struct layoutdriver_io_operations {
 	 * a set_layout call to set the opaque layout in the layout driver.*/
 	struct pnfs_layout_hdr * (*alloc_layout) (struct inode *inode);
 	void (*free_layout) (struct pnfs_layout_hdr *);
-	struct pnfs_layout_segment * (*alloc_lseg) (struct pnfs_layout_type *layoutid, struct nfs4_pnfs_layoutget_res *lgr);
+	struct pnfs_layout_segment * (*alloc_lseg) (struct pnfs_layout_hdr *layoutid, struct nfs4_pnfs_layoutget_res *lgr);
 	void (*free_lseg) (struct pnfs_layout_segment *lseg);
 
 	/* Registration information for a new mounted file system
-- 
1.6.2.5


  reply	other threads:[~2010-08-18 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 14:44 [PATCH 0/11] pnfs-submit rename pnfs_layout_type andros
2010-08-18 14:44 ` [PATCH 01/11] SQUASHME pnfs-submit: rename pnfs_layout_type 1 andros
2010-08-18 14:44   ` [PATCH 02/11] SQUASHME pnfs-submit rename pnfs_layout_type 2 andros
2010-08-18 14:44     ` andros [this message]
2010-08-18 14:44       ` [PATCH 04/11] SQUASHME pnfs-submit rename pnfs_layout_type 4 andros
2010-08-18 14:44         ` [PATCH 05/11] SQUASHME pnfs-submit: rename pnfs_layout_type 5 andros
2010-08-18 14:44           ` [PATCH 06/11] SQUASHME pnfs-submit: rename pnfs_layout_type 6 andros
2010-08-18 14:44             ` [PATCH 07/11] SQUASHME pnfs_submit: rename pnfs_layout_type 7 andros
2010-08-18 14:44               ` [PATCH 08/11] SQUASHME pnfs_submit rename pnfs_layout_type 8 andros
2010-08-18 14:44                 ` [PATCH 09/11] SQUASHME pnfs_submit rename pnfs_layout_type 9 andros
2010-08-18 14:44                   ` [PATCH 10/11] SQUASHME pnfs_submit rename pnfs_layout_type 10 andros
2010-08-18 14:44                     ` [PATCH 11/11] SQUASHME pnfs_submit rename pnfs_layout_type 11 andros

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=1282142658-21579-4-git-send-email-andros@netapp.com \
    --to=andros@netapp.com \
    --cc=bhalevy@panasas.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).