linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: tao.peng@emc.com
Cc: rees@umich.edu, bergwolf@gmail.com, Trond.Myklebust@netapp.com,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/9] pnfsblock patches
Date: Wed, 30 Nov 2011 15:05:09 +0200	[thread overview]
Message-ID: <4ED62A05.9040309@tonian.com> (raw)
In-Reply-To: <F19688880B763E40B28B2B462677FBF805E3A4B053@MX09A.corp.emc.com>

I merged patches 8 and 9 into my tree

Benny

On 2011-11-30 04:37, tao.peng@emc.com wrote:
>> -----Original Message-----
>> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-owner@vger.kernel.org] On Behalf Of Jim Rees
>> Sent: Wednesday, November 30, 2011 2:44 AM
>> To: Peng Tao
>> Cc: Trond.Myklebust@netapp.com; linux-nfs@vger.kernel.org
>> Subject: Re: [PATCH 0/9] pnfsblock patches
>>
>> Peng Tao wrote:
>>
>>   Hi, Trond,
>>
>>   Following are some bugfix and improvements for blocklayout driver. All have been
>>   sent to the list before and have been tested for several weeks.
>>
>> Patches 2/9 and 8/9 are missing again.  I wonder why these particular
>> patches are getting filtered out?
> I have received these patches in both my gmail box and emc mail box. So I guess vger dropped them, again... Somehow it thinks I'm a spammer?
> I attached 2/9, 8/9, 9/9 here...
> 
> Thanks,
> Tao
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2011-11-30 13:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03  4:46 [PATCH 0/9] pnfsblock patches Peng Tao
2011-11-29 18:44 ` Jim Rees
2011-11-30  2:37   ` tao.peng
2011-11-30 13:05     ` Benny Halevy [this message]
2011-11-30 13:25       ` Peng Tao
2011-11-29 21:38 ` Boaz Harrosh
2011-11-29 22:58   ` Jim Rees
2011-11-29 23:39     ` Boaz Harrosh
2011-11-30  2:44       ` tao.peng
2011-12-03  4:46 ` [PATCH 1/9] pnfsblock: cleanup bl_mark_sectors_init Peng Tao
2011-12-03  4:46 ` [PATCH 3/9] pnfsblock: move find lock page logic out of bl_write_pagelist Peng Tao
2011-12-03  4:46 ` [PATCH 4/9] pnfsblock: set read/write tk_status to pnfs_error Peng Tao
2011-12-03  4:46 ` [PATCH 5/9] pnfsblock: remove rpc_call_ops from struct parallel_io Peng Tao
2011-12-03  4:46 ` [PATCH 6/9] pnfsblock: clean up _add_entry Peng Tao
2011-12-03  4:46 ` [PATCH 7/9] pnfsblock: alloc short extent before submit bio Peng Tao

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=4ED62A05.9040309@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bergwolf@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    --cc=tao.peng@emc.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).