xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Giridhar Maruthy <giridhar.maruthy@linaro.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [XenARM]  Testing xen-arm on Arndale
Date: Wed, 17 Jul 2013 17:38:39 +0100	[thread overview]
Message-ID: <51E6C88F.4010103@linaro.org> (raw)
In-Reply-To: <CAHuqX+Hks5KNVB5xEAT7ctp-B4wgNOE-zMaABp9t+y+S4P7kTw@mail.gmail.com>

On 07/17/2013 01:53 PM, Giridhar Maruthy wrote:
> Thanks Julien for the response.
> 
> Following is my environment:
> Dom0 kernel: git://xenbits.xen.org/people/julieng/linux-arm.git
> (arndale branch) version 3.9-rc4
> Xen : git://xenbits.xen.org/people/julieng/xen-unstable.git (branch
> dev-arm) version 4.4 unstable

As specified on the wiki page, you should use:
git://xenbits.xen.org/xen.git

The branch dev-arm, in my git tree, is not intended to be use by
user/developper. It mostly contains debugging patch and my on-going work
on Xen. I will rename this branch dev-arm to avoid confusion.

Currently, this branch doesn't work with linux 3.9 because the DTS is
incomplete.

-- 
Julien

  reply	other threads:[~2013-07-17 16:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJWjLtp3yQhL1x9L=Lb6zq19Qc0dJwfjarwgd1NxFYNxXfER=g@mail.gmail.com>
2013-03-26 16:04 ` Testing xen-arm on Arndale Anthony PERARD
2013-03-26 19:29   ` Julien Grall
2013-03-27  0:40     ` Sengul Thomas
2013-03-27 10:48       ` [XenARM] " Stefano Stabellini
2013-03-27  8:23     ` Sengul Thomas
2013-03-27 11:42       ` Sengul Thomas
2013-03-27 11:57         ` Stefano Stabellini
2013-03-28 10:25           ` Sengul Thomas
2013-03-28 12:09             ` Stefano Stabellini
2013-03-29  6:57               ` Sengul Thomas
2013-03-29 12:42                 ` Julien Grall
2013-03-29 12:50                   ` Stefano Stabellini
2013-03-30  3:40                   ` Sengul Thomas
2013-04-01 14:15                     ` Julien Grall
2013-04-03  9:28                       ` See-Hwan Yoo
2013-04-03 10:52                         ` Stefano Stabellini
2013-04-03 11:57                           ` See-Hwan Yoo
2013-04-03 13:22                             ` Julien Grall
2013-04-04  2:06                               ` See-Hwan Yoo
2013-04-04 13:38                                 ` Julien Grall
2013-04-05  1:26                                   ` See-Hwan Yoo
2013-04-05 11:34                                     ` Stefano Stabellini
2013-04-05 13:34                                       ` Julien Grall
2013-04-03 13:37                             ` Stefano Stabellini
2013-04-10 11:44                               ` Ian Campbell
2013-07-16  6:33     ` [XenARM] " Giridhar Maruthy
     [not found]       ` <CAHuqX+GCwz8RhC3AxKKWzF5PKf4MWWqboHnHiqde7GfzpZ+T6w@mail.gmail.com>
2013-07-17  9:39         ` Julien Grall
2013-07-17 12:53           ` Giridhar Maruthy
2013-07-17 16:38             ` Julien Grall [this message]
2013-07-18  9:58               ` Giridhar Maruthy
2013-07-18 13:43                 ` Giridhar Maruthy
2013-07-18 13:54                   ` Julien Grall
2013-07-18 14:22                     ` Giridhar Maruthy

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=51E6C88F.4010103@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=anthony.perard@citrix.com \
    --cc=giridhar.maruthy@linaro.org \
    --cc=xen-devel@lists.xen.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).