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
prev parent reply other threads:[~2011-11-02 19:01 UTC|newest]
Thread overview: 6+ 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
[not found] ` <4EAAFED8.7020600-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-10-29 17:24 ` Trond Myklebust
2011-10-31 17:49 ` Boaz Harrosh
[not found] ` <4EAEDFA6.4080303-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-10-31 21:34 ` Boaz Harrosh
2011-11-01 17:42 ` Boaz Harrosh
[not found] ` <4EB02FA2.80204-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-11-02 19:01 ` Boaz Harrosh [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=4EB19399.10402@panasas.com \
--to=bharrosh-c4p08nqkorlbdgjk7y7tuq@public.gmane.org \
--cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.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).