From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/7] pnfs-submit api touch ups
Date: Thu, 06 May 2010 22:20:15 +0300 [thread overview]
Message-ID: <4BE3166F.7060800@panasas.com> (raw)
After rebasing everything on top of Andy and Fred patchsets I propose the following:
[PATCH 1/2] SQUASHME: pnfs-submit: have initialize_mountpoint return status
[PATCH 2/2] SQUASHME: pnfs-submit: pass struct nfs_server * to getdeviceinfo
[PATCH 3/5] pnfs-post-submit: pass struct nfs_server * to getdevicelist
[PATCH 4/5] pnfs-post-submit: pass mntfh down the init_pnfs path
[PATCH 5/5] FIXME: pnfs-post-submit: per mount layout driver private data
[PATCH 6/6] SQUASHME: pnfs-block: convert APIs pnfs-post-submit
[PATCH 7/7] SQUASHME: pnfs-obj: convert APIs pnfs-post-submit
next reply other threads:[~2010-05-06 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 19:20 Benny Halevy [this message]
2010-05-06 19:22 ` [PATCH 1/2] SQUASHME: pnfs-submit: have initialize_mountpoint return status Benny Halevy
2010-05-06 19:23 ` [PATCH 2/2] SQUASHME: pnfs-submit: pass struct nfs_server * to getdeviceinfo Benny Halevy
2010-05-06 19:23 ` [PATCH 3/5] pnfs-post-submit: pass struct nfs_server * to getdevicelist Benny Halevy
2010-05-06 19:23 ` [PATCH 4/5] pnfs-post-submit: pass mntfh down the init_pnfs path Benny Halevy
2010-05-06 19:23 ` [PATCH 5/5] FIXME: pnfs-post-submit: per mount layout driver private data Benny Halevy
2010-05-09 16:25 ` Boaz Harrosh
2010-05-10 14:24 ` Andy Adamson
2010-05-11 8:46 ` Boaz Harrosh
2010-05-11 15:02 ` William A. (Andy) Adamson
2010-05-06 19:24 ` [PATCH 6/6] SQUASHME: pnfs-block: convert APIs pnfs-post-submit Benny Halevy
2010-05-06 19:24 ` [PATCH 7/7] SQUASHME: pnfs-obj: " Benny Halevy
2010-05-06 19:33 ` [PATCH 0/7] pnfs-submit api touch ups William A. (Andy) Adamson
[not found] ` <o2o89c397151005061233vcaefdd27s4513be2b641348a2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-06 20:24 ` Benny Halevy
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=4BE3166F.7060800@panasas.com \
--to=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 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.