linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: pnfs git tree status pnfs-all-2.6.37-rc3-2010-11-23
Date: Tue, 23 Nov 2010 16:21:37 +0200	[thread overview]
Message-ID: <4CEBCDF1.4010705@panasas.com> (raw)
In-Reply-To: <4CE1604E.1070902@panasas.com>

This is a minor update to the linux-pnfs tree.
Rebased over v2.6.37-rc3, and dropped old version of
Trond's patch 88ce1e4 NFS: Fix a couple of regressions in readdir.
in favor of the new version merged in v2.6.37-rc3.

On 2010-11-15 18:31, Benny Halevy wrote:

Cumulative patches can be generated from
git://linux-nfs.org/~bhalevy/linux-pnfs.git
using
git diff v2.6.37-rc3 pnfs-all-2.6.37-rc3-2010-11-23

Or, they can be downloaded from the wiki at:
http://wiki.linux-nfs.org/wiki/index.php/PNFS_Development_Git_tree

Latest patches that went in since pnfs-all-2.6.37-rc1-2010-11-03:

pnfs:
  Benny Halevy     f272cdf SQUASHME: pnfs: move synchronize_rcu out side of spin_lock

  reply	other threads:[~2010-11-23 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 15:29 pnfs git tree status pnfs-all-2.6.37-rc1-2010-11-03 Benny Halevy
2010-11-15 16:31 ` pnfs git tree status pnfs-all-2.6.37-rc1-2010-11-15 Benny Halevy
2010-11-23 14:21   ` Benny Halevy [this message]
2011-01-27 20:37     ` pnfs git tree status pnfs-all-2.6.37-2011-01-06 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=4CEBCDF1.4010705@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 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).