From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "Juergen Gross" <jgross@suse.com>,
"Lars Kurth" <lars.kurth@citrix.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
julien.grall@arm.com, "Paul Durrant" <paul.durrant@citrix.com>,
committers@xenproject.org, xen-devel@lists.xenproject.org,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: linux-arm-xen branch, commit access, etc.
Date: Fri, 20 Oct 2017 20:10:56 +0100 [thread overview]
Message-ID: <CAEC2CxpWHsSREbPFWUE2SzisfxoTHZUs529aeMKm-YHAoFJ0YQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1710201051090.27209@sstabellini-ThinkPad-X260>
[-- Attachment #1.1: Type: text/plain, Size: 1829 bytes --]
Hi,
Sorry for the formatting.
On 20 Oct 2017 19:06, "Stefano Stabellini" <sstabellini@kernel.org> wrote:
CC'ing Julien
On Fri, 20 Oct 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [Xen-devel] linux-arm-xen branch, commit
access, etc."):
> > On Fri, 20 Oct 2017, Konrad Rzeszutek Wilk wrote:
> > > 3. Use upstream released kernels. Follow them when they are released.
> >
> > I agree with Konrad. The reason why that branch is there is that
> > initially we needed a couple of patches to run Linux on Exynos5 boards
> > (Arndale). Today, vanilla releases should work. For example, 4.13 has
> > everything we need as far as I can tell. I think it is time to remove
> > the special branch.
>
> So vanilla kernels are going to work well on our new ARM64 boxes, eg
> ThunderX, and whatever we come up with for new ARM32 testing too ?
I think so: ThunderX and other server platforms should be more
"standard" than small embedded boards. But if we decide to buy some
small and cheap ARM32 boards, such as Linaro HiKey, they tend to still
require special kernel trees.
It is what you wish :). For instance Thunder-X support has been fully made
upstream (ACPI + DT) only recently.
In other words: I think we should be able to get rid of the special tree
for the hardware that we have today, but I cannot guarantee that we
won't ever need it in the future.
IIRC we are going to get some renesas board recently. Do you know if
upstream will work?
Julien, do you think we need to keep a special linux tree around for Xen
on ARM testing in OSSTest or we can start using vanilla kernel releases?
I would love to get rid of it, if you know of any reasons why we have to
keep it, this is the time to speak :-)
I think it would be better to keep aroundSome platform may be available
before the code is merged.
Cheers,
[-- Attachment #1.2: Type: text/html, Size: 3100 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-20 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 14:34 linux-arm-xen branch, commit access, etc Ian Jackson
2017-10-20 15:56 ` Konrad Rzeszutek Wilk
2017-10-20 17:17 ` Stefano Stabellini
2017-10-20 17:45 ` Ian Jackson
2017-10-20 18:04 ` Stefano Stabellini
2017-10-20 19:10 ` Julien Grall [this message]
2017-10-23 21:33 ` Stefano Stabellini
2017-11-02 13:34 ` Julien Grall
2017-12-05 15:46 ` Julien Grall
2017-12-05 17:42 ` Ian Jackson
2017-12-05 17:57 ` Julien Grall
2017-12-05 18:28 ` [OSSTEST PATCH] linux-arm-xen: Get from shared arm/linux.git xenbits tree Ian Jackson
2017-12-05 18:30 ` Julien Grall
2017-12-05 18:34 ` Stefano Stabellini
2017-12-05 18:41 ` Ian Jackson
2017-12-05 18:42 ` Julien Grall
2017-12-08 15:09 ` linux-xen-arm branch update Julien Grall
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=CAEC2CxpWHsSREbPFWUE2SzisfxoTHZUs529aeMKm-YHAoFJ0YQ@mail.gmail.com \
--to=julien.grall@linaro.org \
--cc=boris.ostrovsky@oracle.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=paul.durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).