From: Boaz Harrosh <bharrosh@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: Re: [osd-dev] [patchset 0/8] pnfs-obj: Move to ORE for v3.2 merge window
Date: Wed, 2 Nov 2011 12:01:45 -0700 [thread overview]
Message-ID: <4EB19399.10402@panasas.com> (raw)
In-Reply-To: <4EB02FA2.80204@panasas.com>
On 11/01/2011 10:42 AM, Boaz Harrosh wrote:
> On 10/31/2011 02:34 PM, Boaz Harrosh wrote:
>>
>> Hi trond
>>
>> I just re-checked. Compiled both i386 an x86_64 allmodconfig and even
>> merge with latest linus tree. I sign on these patches.
>>
>> Again they were in linux-next as is, untouched based on exofs tree.
>> And now based on Linus/master [f362f98] They compile and run.
>>
>> I'll re-post them just in case you decide to need them, as reply to
>> this mail.
>>
>> Thanks
>> Boaz
>
> Hi Trond
>
> We just had a linux-next tree "linux-next: Tree for Nov 1"
> I looked through all the compile logs for the different
> arches it is all clean. So I guess it is ready as it can be.
>
Trond? ping? It is possible that the merge window will end this
Friday/Saturday.
What prevents the pull?
> Cheers
> Boaz
Thanks
Boaz
WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
To: Trond Myklebust
<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
open-osd <osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org>
Subject: Re: [osd-dev] [patchset 0/8] pnfs-obj: Move to ORE for v3.2 merge window
Date: Wed, 2 Nov 2011 12:01:45 -0700 [thread overview]
Message-ID: <4EB19399.10402@panasas.com> (raw)
In-Reply-To: <4EB02FA2.80204-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
On 11/01/2011 10:42 AM, Boaz Harrosh wrote:
> On 10/31/2011 02:34 PM, Boaz Harrosh wrote:
>>
>> Hi trond
>>
>> I just re-checked. Compiled both i386 an x86_64 allmodconfig and even
>> merge with latest linus tree. I sign on these patches.
>>
>> Again they were in linux-next as is, untouched based on exofs tree.
>> And now based on Linus/master [f362f98] They compile and run.
>>
>> I'll re-post them just in case you decide to need them, as reply to
>> this mail.
>>
>> Thanks
>> Boaz
>
> Hi Trond
>
> We just had a linux-next tree "linux-next: Tree for Nov 1"
> I looked through all the compile logs for the different
> arches it is all clean. So I guess it is ready as it can be.
>
Trond? ping? It is possible that the merge window will end this
Friday/Saturday.
What prevents the pull?
> Cheers
> Boaz
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-02 19:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 19:13 [patchset 0/8] pnfs-obj: Move to ORE for v3.2 merge window Boaz Harrosh
2011-10-29 17:24 ` Trond Myklebust
2011-10-29 17:24 ` Trond Myklebust
2011-10-31 17:49 ` Boaz Harrosh
2011-10-31 21:34 ` Boaz Harrosh
2011-10-31 21:34 ` Boaz Harrosh
2011-10-31 21:45 ` [PATCH 1/8] pnfs-obj: Remove redundant EOF from objlayout_io_state Boaz Harrosh
2011-10-31 22:24 ` Trond Myklebust
2011-10-31 22:45 ` Boaz Harrosh
2011-10-31 23:23 ` Boaz Harrosh
2011-10-31 23:29 ` Trond Myklebust
2011-10-31 23:59 ` Boaz Harrosh
2011-11-01 2:25 ` Trond Myklebust
2011-10-31 21:45 ` [PATCH 2/8] pnfs-obj: Return PNFS_NOT_ATTEMPTED in case of read/write_pagelist Boaz Harrosh
2011-10-31 21:47 ` [PATCH 3/8] pnfs-obj: Get rid of objlayout_{alloc,free}_io_state Boaz Harrosh
2011-10-31 22:03 ` [PATCH 4/8] pnfs-obj: Rename objlayout_io_state => objlayout_io_res Boaz Harrosh
2011-10-31 22:04 ` [PATCH 5/8] pnfs-obj: move to ore 01: ore_layout & ore_components Boaz Harrosh
2011-10-31 22:15 ` [PATCH 6/8] pnfs-obj: move to ore 02: move to ORE Boaz Harrosh
2011-10-31 22:16 ` [PATCH 7/8] pnfs-obj: move to ore 03: Remove old raid engine Boaz Harrosh
2011-10-31 22:16 ` [PATCH 8/8] pnfs-obj: Support for RAID5 read-4-write interface Boaz Harrosh
2011-11-01 17:42 ` [patchset 0/8] pnfs-obj: Move to ORE for v3.2 merge window Boaz Harrosh
2011-11-02 19:01 ` Boaz Harrosh [this message]
2011-11-02 19:01 ` [osd-dev] " 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=4EB19399.10402@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--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.