All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii.anisov@globallogic.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OMAP5 port.
Date: Wed, 13 Mar 2013 17:51:48 +0200	[thread overview]
Message-ID: <CAGQvs6jtMpyyWw_bftFfGhKV2oTayWTmSt9AZJ-edUmT46-aDg@mail.gmail.com> (raw)
In-Reply-To: <1363186860.32410.196.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1306 bytes --]

Ian,

For sure we took the latest hypervisor from xen.git master branch, we have
our specific patches ontop of this commit:

commit ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc
Author: Liu Jinsong <jinsong.liu@intel.com>
Date:   Thu Feb 28 09:22:41 2013 +0100

What was the master HEAD on start of this March.

I ask about the suitable kernel patch set we could port on our 3.4 kernel.

Sincerely,
Andrii Anisov.

On Wed, Mar 13, 2013 at 5:01 PM, Ian Campbell <Ian.Campbell@citrix.com>wrote:

> On Wed, 2013-03-13 at 14:55 +0000, Andrii Anisov wrote:
> > We are doing an experimental porting XEN on a TI OMAP5 based board.
>
> Cool!
>
> [...]
> > One more question: is
> > http://lists.xen.org/archives/html/xen-devel/2012-09/msg01091.html the
> > latest version of the patchset?  Is it available as a tarball?
>
> That is an ancient and no doubt very incomplete set of patches, lots has
> changed since September last year!
>
> Everything which you need is in the mainline xen.git repository already:
>         http://xenbits.xen.org/gitweb/?p=xen.git
>         http://wiki.xen.org/wiki/Xen_Repositories
> The master branch should be your first port of call.
>
> I didn't bother replying to the other bits of your mail since they are
> almost certainly due to running such an ancient hypervisor.
>
> Ian.
>
>

[-- Attachment #1.2: Type: text/html, Size: 2302 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-03-13 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 14:55 OMAP5 port Andrii Anisov
2013-03-13 15:01 ` Ian Campbell
2013-03-13 15:51   ` Andrii Anisov [this message]
2013-03-13 15:53     ` Ian Campbell
2013-03-13 16:50       ` Andrii Anisov
2013-03-13 16:56         ` Ian Campbell
2013-03-14 16:42         ` Stefano Stabellini
2013-03-14 17:45           ` Anthony PERARD
2013-03-22 13:56       ` Stefano Stabellini
2013-03-22 15:17         ` Chen Baozi
2013-03-22 15:30           ` Anthony PERARD
2013-03-28  9:36             ` Chen Baozi
2013-04-09 13:39               ` Andrii Anisov

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=CAGQvs6jtMpyyWw_bftFfGhKV2oTayWTmSt9AZJ-edUmT46-aDg@mail.gmail.com \
    --to=andrii.anisov@globallogic.com \
    --cc=Ian.Campbell@citrix.com \
    --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 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.