From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org, Andy Adamson <andros@netapp.com>
Subject: [PATCH 02/11] SQUASHME pnfs-submit rename pnfs_layout_type 2
Date: Wed, 18 Aug 2010 10:44:09 -0400 [thread overview]
Message-ID: <1282142658-21579-3-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1282142658-21579-2-git-send-email-andros@netapp.com>
From: Andy Adamson <andros@netapp.com>
squash into pnfs_submit: filelayout alloc_layout and free_layout
Signed-off-by: Andy Adamson <andros@netapp.com>
---
fs/nfs/nfs4filelayout.c | 6 +++---
fs/nfs/nfs4filelayout.h | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
index fea1772..fa08540 100644
--- a/fs/nfs/nfs4filelayout.c
+++ b/fs/nfs/nfs4filelayout.c
@@ -282,10 +282,10 @@ filelayout_write_pagelist(struct nfs_write_data *data, unsigned nr_pages, int sy
/*
* Create a filelayout layout structure and return it. The pNFS client
- * will use the pnfs_layout_type type to refer to the layout for this
+ * will use the pnfs_layout_hdr type to refer to the layout for this
* inode from now on.
*/
-static struct pnfs_layout_type *
+static struct pnfs_layout_hdr *
filelayout_alloc_layout(struct inode *inode)
{
struct nfs4_filelayout *flp;
@@ -297,7 +297,7 @@ filelayout_alloc_layout(struct inode *inode)
/* Free a filelayout layout structure */
static void
-filelayout_free_layout(struct pnfs_layout_type *lo)
+filelayout_free_layout(struct pnfs_layout_hdr *lo)
{
dprintk("NFS_FILELAYOUT: freeing layout\n");
kfree(FILE_LO(lo));
diff --git a/fs/nfs/nfs4filelayout.h b/fs/nfs/nfs4filelayout.h
index f8f7c05..c851919 100644
--- a/fs/nfs/nfs4filelayout.h
+++ b/fs/nfs/nfs4filelayout.h
@@ -62,7 +62,7 @@ struct nfs4_filelayout_segment {
};
struct nfs4_filelayout {
- struct pnfs_layout_type fl_layout;
+ struct pnfs_layout_hdr fl_layout;
u32 stripe_unit;
};
@@ -70,7 +70,7 @@ extern struct nfs_fh *
nfs4_fl_select_ds_fh(struct pnfs_layout_segment *lseg, loff_t offset);
static inline struct nfs4_filelayout *
-FILE_LO(struct pnfs_layout_type *lo)
+FILE_LO(struct pnfs_layout_hdr *lo)
{
return container_of(lo, struct nfs4_filelayout, fl_layout);
}
--
1.6.2.5
next prev parent 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 ` andros [this message]
2010-08-18 14:44 ` [PATCH 03/11] SQUASHME pnfs-submit rename pnfs_layout_type 3 andros
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-3-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).