From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Cc: Steve Dickson <steved@redhat.com>
Subject: Re: pnfs git tree status pnfs-all-2.6.34-rc6-2010-05-06 pnfs-all-2.6.33-2010-05-06
Date: Fri, 07 May 2010 00:15:08 +0300 [thread overview]
Message-ID: <4BE3315C.9090908@panasas.com> (raw)
In-Reply-To: <4BE330E6.70707@panasas.com>
On May. 07, 2010, 0:13 +0300, Benny Halevy <bhalevy@panasas.com> wrote:
> I released the following today:
>
> pnfs-all-2.6.33-2010-05-06
> pnfs-all-2.6.34-rc6-2010-05-06
>
> As usual, cumulative patches can be generated from
> git://linux-nfs.org/~bhalevy/linux-pnfs.git
> using
> git diff v2.6.33 pnfs-all-2.6.33-2010-05-06
> git diff v2.6.34-rc6 pnfs-all-2.6.34-rc6-2010-05-06
>
> Or, they can be downloaded from the wiki at:
> http://wiki.linux-nfs.org/wiki/index.php/PNFS_Development_Git_tree
>
> Latest patches (since 2010-04-29):
>
> pnfs-submit:
> Andy Adamson (1):
> SQUASHME pnfs: restore state recovery in async handler
>
> Benny Halevy (2):
> SQUASHME: pnfs-submit: have initialize_mountpoint return status
> SQUASHME: pnfs-submit: pass struct nfs_server * to getdeviceinfo
>
> Fred Isaman (4):
> SQUASHME: pnfs_submit: Revert the pnfs_write_end part of "pnfs: commit and pnfs_write_end"
> SQUASHME: pnfs_submit: Revert "pnfs: pnfs_modify_new_request"
> SQUASHME: pnfs_submit: Revert "pnfs: propagate fsdata into nfs_create_request"
> SQUASHME: pnfs_submit: Revert "pnfs: pnfs_do_flush"
>
> Zhang Jingwang (1):
> SQUASHME: pnfs-submit: Free layoutcommit_data when error occurs in setup
>
> pnfs:
> Andy Adamson (4):
> pnfs_post_submit: restore CB_NOTIFY_DEVICEID
> pnfs_post_submit: restore GETDEVICELIST
> pnfs_post_submit: restore ds_wsize and ds_rsize
> pnfs_post_submit: restore get_blocksize policy operation
>
> Benny Halevy (3):
> pnfs-post-submit: pass struct nfs_server * to getdevicelist
> pnfs-post-submit: pass mntfh down the init_pnfs path
> FIXME: pnfs-post-submit: per mount layout driver private data
>
> Fred Isaman (4):
> pnfs_post_submit: Restore "pnfs: pnfs_do_flush"
> pnfs_post_submit: Restore "pnfs: propagate fsdata into nfs_create_request"
> pnfs_post_submit: Restore "pnfs: pnfs_modify_new_request"
> pnfs_post_submit: Revert the pnfs_write_end part of "pnfs: commit and pnfs_write_end"
>
> pnfs-block:
> Benny Halevy (1):
> SQUASHME: pnfs-block: convert APIs pnfs-post-submit
>
> Zhang Jingwang (1):
> SQAUSHME: blocklayoutdriver: NULL pointer reference when committing too many extents
>
> pnfs-obj-all:
> Benny Halevy (1):
> SQUASHME: pnfs-obj: convert APIs pnfs-post-submit
>
>
And latest patches in pnfs-2.6.33:
pnfs-all-2.6.33:
Zhang Jingwang (2):
SQAUSHME: blocklayoutdriver: NULL pointer reference when committing too many extents
pnfs: Free layoutcommit_data when error occurs in setup
next prev parent reply other threads:[~2010-05-06 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 17:16 pnfs git tree status 2010-04-29 Benny Halevy
2010-05-06 21:13 ` pnfs git tree status pnfs-all-2.6.34-rc6-2010-05-06 pnfs-all-2.6.33-2010-05-06 Benny Halevy
2010-05-06 21:15 ` Benny Halevy [this message]
2010-05-17 20:45 ` pnfs git tree status pnfs-all-2.6.34-2010-05-17 Benny Halevy
2010-07-01 18:57 ` pnfs git tree status pnfs-all-2.6.34-2010-07-01 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=4BE3315C.9090908@panasas.com \
--to=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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).