linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
To: Trond Myklebust
	<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: NFS list <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	open-osd <osd-dev-yNzVSZO3znNg9hUCZPvPmw@public.gmane.org>,
	linux-fsdevel
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patchset 0/8] pnfs-obj: Move to ORE for v3.2 merge window
Date: Mon, 31 Oct 2011 14:34:37 -0700	[thread overview]
Message-ID: <4EAF146D.5060507@panasas.com> (raw)
In-Reply-To: <4EAEDFA6.4080303-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>

On 10/31/2011 10:49 AM, Boaz Harrosh wrote:
> On 10/29/2011 10:24 AM, Trond Myklebust wrote:
>> Hi Boaz,
>>
>> Have you tested these patches in linux-next? If so, I can pull them in
>> from open-osd.org and send them with the next merge. If not, I think
>> patches (as soon as possible!) would be better. I'll commit them to
>> nfs-for-next, and we can try to get them in...
>>
>> Cheers
>>   Trond
>>
> 
> Hi Trond.
> 
> These patches where in next since before the BAT when I sent them to the
> list, then based on my exofs tree. I have now rebased on Linus master
> based on my pull bits and Yours, and again they where in next since
> Thursday. But the big question is did we have linux-next in that time
> frame because I thought Stephen was on vacation and the last linux-next
> was around Oct 20th?
> 
> Any way both our bits where in Linux next since Oct 16. The patches are
> rebased but completely unchanged.
> 
> Is there some tests I should make, other then compile oldmodconfig x86_64
> and x86_32? I wish I had setup for more compilers. 
> 
> But I'd say the risk is very low since the exact patches did sit in next.
> And after rebase I run a compile and a short test run.
> 
> Any way I can post the patches. Give me an hour
> Boaz
> 

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
--
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

  parent reply	other threads:[~2011-10-31 21:34 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 [this message]
2011-11-01 17:42           ` Boaz Harrosh
     [not found]             ` <4EB02FA2.80204-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
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=4EAF146D.5060507@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).