From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/7] pnfs-submit layoutdriver api parameter consolidation
Date: Thu, 15 Jul 2010 12:13:47 -0400 [thread overview]
Message-ID: <1279210434-2772-1-git-send-email-andros@netapp.com> (raw)
Compile fix.
0001-SQUASHME-pnfs-submit-fix-CONFIG_NFS_V4_1-not-set-com.patch
The read_pagelist, write_pagelist, and commit layoutdriver io operations
parameters are all serviced by either nfs_write_data or nfs_read_data
fields. Just pass in the data structs.
0002-SQUASHME-pnfs-submit-consolidate-read_pagelist-param.patch
0003-SQUASHME-pnfs-submit-filelayout-use-new-read_pagelis.patch
0004-SQUASHME-pnfs-submit-consolidate-write_pagelist-para.patch
0005-SQUASHME-pnfs-submit-filelayout-use-new-write_pageli.patch
0006-SQUASHME-pnfs-submit-consolidate-commit-parameters.patch
0007-SQUASHME-pnfs-submit-filelayout_commit-use-new-API.patch
Testing
CONFIG_NFS_V4_1 set:
Connectathon passes
CONFIG_NFS_V4_1 not set:
Connectathon passes
-->Andy
next reply other threads:[~2010-07-15 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 16:13 andros [this message]
2010-07-15 16:13 ` [PATCH 1/7] SQUASHME pnfs-submit fix CONFIG_NFS_V4_1 not set compile error andros
2010-07-15 16:13 ` [PATCH 2/7] SQUASHME pnfs-submit consolidate read_pagelist parameters andros
2010-07-15 16:13 ` [PATCH 3/7] SQUASHME pnfs-submit filelayout use new read_pagelist API andros
2010-07-15 16:13 ` [PATCH 4/7] SQUASHME pnfs-submit consolidate write_pagelist parameters andros
2010-07-15 16:13 ` [PATCH 5/7] SQUASHME pnfs-submit filelayout use new write_pagelist API andros
2010-07-15 16:13 ` [PATCH 6/7] SQUASHME pnfs-submit consolidate commit parameters andros
2010-07-15 16:13 ` [PATCH 7/7] SQUASHME pnfs-submit filelayout_commit use new API andros
2010-07-20 4:26 ` [PATCH 4/7] SQUASHME pnfs-submit consolidate write_pagelist parameters Benny Halevy
2010-07-20 4:33 ` Benny Halevy
2010-07-20 13:51 ` William A. (Andy) Adamson
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=1279210434-2772-1-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).