All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: NFS list <linux-nfs@vger.kernel.org>, open-osd <osd-dev@open-osd.org>
Subject: Re: [PATCHSET 0/4] exofs & pnfsd-exofs assorted changes
Date: Thu, 11 Aug 2011 15:19:10 +0300	[thread overview]
Message-ID: <4E43C8BE.9040108@tonian.com> (raw)
In-Reply-To: <4E42F3E3.8050006@panasas.com>

On 2011-08-11 00:10, Boaz Harrosh wrote:
> 
> Submitted are, a changes to upstream exofs, and some proper fixes
> to pnfsd-exofs.
> 
> the patches:
> [PATCH 1/4] exofs: Remove unused data_map member from exofs_sb_info
> 
> 	This patch will be put in linux-next for the 3.2 merge window
> 
> [PATCH 2/4] SQUASHME: pnfsd-exofs: Convert to ORE (2)
> [PATCH 3/4] ore: Make ore_calc_stripe_info EXPORT_SYMBOL
> [PATCH 4/4] pnfsd-exofs: Serve out a single group layout at a time
> 
> 	These patches are for the pnfsd tree, including the ore
> 	one which has users only in the pnfsd tree for now.
> 
> Thanks
> Boaz
> 

Merged into pnfsd-exofs. Thanks!

Benny

P.S. I don't think my Panasas email address is still active
no need to send stuff there...

  parent reply	other threads:[~2011-08-11 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 21:10 [PATCHSET 0/4] exofs & pnfsd-exofs assorted changes Boaz Harrosh
2011-08-10 21:15 ` [PATCH 1/4] exofs: Remove unused data_map member from exofs_sb_info Boaz Harrosh
2011-08-10 21:16 ` [PATCH 2/4] SQUASHME: pnfsd-exofs: Convert to ORE (2) Boaz Harrosh
2011-08-10 21:17 ` [PATCH 3/4] ore: Make ore_calc_stripe_info EXPORT_SYMBOL Boaz Harrosh
2011-08-10 21:18 ` [PATCH 4/4] pnfsd-exofs: Serve out a single group layout at a time Boaz Harrosh
2011-08-11 12:19 ` Benny Halevy [this message]
2011-08-11 18:18   ` [PATCHSET 0/4] exofs & pnfsd-exofs assorted changes Boaz Harrosh

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=4E43C8BE.9040108@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osd-dev@open-osd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.