From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jim Rees <rees@umich.edu>
Cc: Peng Tao <bergwolf@gmail.com>,
linux-nfs@vger.kernel.org, mdw@umich.edu, honey@citi.umich.edu
Subject: Re: [PATCH RESEND 0/9] pnfsblock patches for 3.3 post-rc1
Date: Wed, 11 Jan 2012 14:47:55 -0500 [thread overview]
Message-ID: <1326311275.26351.2.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20120110161406.GA8994@umich.edu>
On Tue, 2012-01-10 at 11:14 -0500, Jim Rees wrote:
> Peng Tao wrote:
>
> These are pnfsblock patches rebased on top of nfs-for-3.3. All patches
> were sent to list before and merged by Benny.
>
> Once again, 8/9 and 9/9 failed to make it to the list. Are these available
> via git?
I appear also to be missing 2/9 here...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2012-01-11 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 14:30 [PATCH RESEND 0/9] pnfsblock patches for 3.3 post-rc1 Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 1/9] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 4/9] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 5/9] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 6/9] pnfsblock: clean up _add_entry Peng Tao
2012-01-10 14:30 ` [PATCH RESEND 7/9] pnfsblock: alloc short extent before submit bio Peng Tao
2012-01-10 16:14 ` [PATCH RESEND 0/9] pnfsblock patches for 3.3 post-rc1 Jim Rees
2012-01-10 16:35 ` Peng Tao
2012-01-11 19:44 ` Trond Myklebust
2012-01-12 15:09 ` Peng Tao
2012-01-11 19:47 ` Trond Myklebust [this message]
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=1326311275.26351.2.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=mdw@umich.edu \
--cc=rees@umich.edu \
/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).