From: Benny Halevy <bhalevy.lists@gmail.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Benny Halevy <bhalevy@panasas.com>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: Re: [PATCHSET 0/8] pnfsd-exofs: New set of exofs pnfs export patches
Date: Tue, 14 Jun 2011 18:24:24 -0400 [thread overview]
Message-ID: <4DF7DF98.6090406@gmail.com> (raw)
In-Reply-To: <4DF7CBE6.1050406@tonian.com>
OK, I took this in under pnfs-all-3.0-rc3-2011-06-14-2
The new tree structure is:
master (at nfs-2.6/nfs-for-bakeathon, based off of v3.0-rc3)
nfs-upstream
pnfs-block
pnfs-obj
nfsd-upstream
nfsd41-all
pnfsd-all
pnfsd-exofs-all
pnfsd-lexp-all
spnfs-all
spnfs-block-all
pnfs-all-latest
+pnfs-obj (that's a merge :)
Benny
On 2011-06-14 17:00, Benny Halevy wrote:
> On 2011-06-14 16:53, Boaz Harrosh wrote:
>>
>> Benny hi
>>
>> I'm submitting a new SQUASHED set of exofs patches. These should completely
>> replace the patches you have now in the pnfsd-exofs{-all} branch
>>
>
> Great, thanks!
>
>> If anyone is curios I'll send a SQUASHME patchset as reply to this mail.
>>
>> I Think the pnfsd-exofs branch should advance down to before the pnfsd-exp-all.
>> It should be the first or second candidate for inclusion.
>
> makes sense
>
>>
>> BTW: You forgot to branch the pnfs-blocks branch last time.
>
> Already fixed... (pnfs-block is there)
>
>>
>> I think that now, since most of the client code is in-tree and all the common code
>> is in. It would be easier to work with a tree that has two separate branches for the
>> 1.block-layout and 2.server branches. And the pnfs-all-latest which merges the two.
>>
>> something like:
>>
>>
>> |----pnfsd(including gfs2_---pnfsd-exofs---pnfsd-exp----pnfsd-spnfs----pnfsd-spnfs-blocks ---|
>> nfs-linux-next--| + --- pnfs-all-latest
>> | --------pnfs-blocks------------------------------------------------------------------------|
>
> Good point, I'll try it out.
>
>>
>> * "+" means a merge
>>
>> It will be much easier to develop this way
>>
>> usual list of patches:
>>
>> [PATCH 1/8] nfs_xdr: Move nfs4_string definition out of #ifdef CONFIG_NFS_V4
>> [PATCH 2/8] exofs: pnfs-tree: Remove pnfs-osd private definitions
>> [PATCH 3/8] pnfs-obj: pnfs_osd_xdr: Remove dead code and cleanup
>>
>> Intended for upstream
>>
>> [PATCH 4/8] pnfsd-exofs: pnfs objects server XDR functions
>> [PATCH 5/8] pnfsd-exofs: Add pNFS export support
>> [PATCH 6/8] pnfsd-exofs: get_device_info implementation.
>> [PATCH 7/8] pnfsd-exofs: Recall layouts on truncate
>> [PATCH 8/8] pnfsd-exofs: layoutreturn pnfs-obj information decoding
>>
>> New exofs pnfs export patches
>
> Where are the patches? :)
>
> Benny
>
>>
>> Thanks
>> Boaz
>>
>>
>> --
>> 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
next prev parent reply other threads:[~2011-06-14 22:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 20:53 [PATCHSET 0/8] pnfsd-exofs: New set of exofs pnfs export patches Boaz Harrosh
2011-06-14 21:00 ` Benny Halevy
2011-06-14 22:24 ` Benny Halevy [this message]
2011-06-14 21:02 ` [PATCH 1/8] nfs_xdr: Move nfs4_string definition out of #ifdef CONFIG_NFS_V4 Boaz Harrosh
2011-06-14 21:02 ` [PATCH 2/8] exofs: pnfs-tree: Remove pnfs-osd private definitions Boaz Harrosh
2011-06-14 21:03 ` [PATCH 4/8] pnfsd-exofs: pnfs objects server XDR functions Boaz Harrosh
2011-06-14 21:03 ` [PATCH 5/8] pnfsd-exofs: Add pNFS export support Boaz Harrosh
2011-06-14 21:03 ` [PATCH 6/8] pnfsd-exofs: get_device_info implementation Boaz Harrosh
2011-06-14 21:03 ` [PATCH 8/8] pnfsd-exofs: layoutreturn pnfs-obj information decoding Boaz Harrosh
2011-06-14 21:20 ` [PATCH 3/8] pnfs-obj: pnfs_osd_xdr: Remove dead code and cleanup Boaz Harrosh
2011-06-14 21:20 ` [PATCH 7/8] pnfsd-exofs: Recall layouts on truncate Boaz Harrosh
2011-06-14 21:32 ` [PATCHSET 0/10] pnfsd-exofs: SQUASHMES that went into last changes Boaz Harrosh
2011-06-14 21:35 ` [PATCH 01/10] SQUASHME: pnfsd-exofs xdr_srv: Wrong type in comments Boaz Harrosh
2011-06-14 21:35 ` [PATCH 02/10] SQUASHME: pnfsd-exofs: Move all Server xdr definisions to separate header Boaz Harrosh
2011-06-14 21:36 ` [PATCH 03/10] SQUASHME: pnfsd-exofs: Prettify pnfs_osd_xdr_srv.h Boaz Harrosh
2011-06-14 21:36 ` [PATCH 04/10] SQUASHME: pnfsd-exofs: Change layout encoding to two pass Boaz Harrosh
2011-06-14 21:36 ` [PATCH 05/10] SQUASHME: pnfsd-exofs: osd_xdr_srv: Convert XDR API to return enum nfsstat4 Boaz Harrosh
2011-06-14 21:36 ` [PATCH 06/10] SQUASHME: pnfsd-exofs: Server xdr definisions were moved to a separate header Boaz Harrosh
2011-06-14 21:36 ` [PATCH 07/10] SQUASHME: pnfsd-exofs: osd_xdr_srv header moved Boaz Harrosh
2011-06-14 21:36 ` [PATCH 08/10] SQUASHME: pnfsd-exofs: layout encoding was Changed to two pass Boaz Harrosh
2011-06-14 21:36 ` [PATCH 09/10] SQUASHME: pnfsd-exofs: Convert XDR API to return enum nfsstat4 Boaz Harrosh
2011-06-14 21:38 ` [PATCH 10/10] SQUASHME: pnfsd-exofs: checkpatch love and a dprint 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=4DF7DF98.6090406@gmail.com \
--to=bhalevy.lists@gmail.com \
--cc=bhalevy@panasas.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 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).