From: Benny Halevy <bhalevy@panasas.com>
To: andros@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] update pnfs-submit-wave3
Date: Mon, 14 Feb 2011 17:16:49 -0500 [thread overview]
Message-ID: <4D59A9D1.5000100@panasas.com> (raw)
In-Reply-To: <1297711909-27015-1-git-send-email-andros@netapp.com>
On 2011-02-14 14:31, andros@netapp.com wrote:
> These two patches bring Benny's git://linux-nfs.org/~bhalevy/linux-pnfs.git
> pnfs-submit-wave3-rev5 branch in line with the wave 3 code just submitted for
> review, caveat some author and patch comment differences.
>
> The 16 patch wave 3 patch set can be found at
> git://linux-nfs.org/projects/andros/nfs-2.6.git wave3-on-nfs-for-next-rev7
>
> 0001-SQUASHME-pnfs_submit-wave3-general-cleanup.patch
> 0002-SQUASHME-pnfs-submit-wave3-avoid-calculating-j-index.patch
>
>
> -->Andy
Looks good to me.
Merged to pnfs-submit-wave3, thanks!
Benny
prev parent reply other threads:[~2011-02-14 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 19:31 [PATCH 0/2] update pnfs-submit-wave3 andros
2011-02-14 19:31 ` [PATCH 1/2] SQUASHME pnfs_submit wave3 general cleanup andros
2011-02-14 19:31 ` [PATCH 2/2] SQUASHME pnfs-submit wave3 avoid calculating j index twice per call andros
2011-02-14 22:16 ` Benny Halevy [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=4D59A9D1.5000100@panasas.com \
--to=bhalevy@panasas.com \
--cc=andros@netapp.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