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>,
"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: Tue, 5 Dec 2017 15:46:12 +0000 [thread overview]
Message-ID: <b82b3feb-720d-d24f-1b49-0aa8f9ff3f6f@linaro.org> (raw)
In-Reply-To: <261a1222-df12-4fe6-0115-808be1c2f80c@linaro.org>
Hi,
Ping? This is going to be very helpful for bringing up osstest on Thunder-X.
Cheers,
On 02/11/17 13:34, Julien Grall wrote:
> Hi,
>
> On 23/10/17 22:33, Stefano Stabellini wrote:
>> On Fri, 20 Oct 2017, Julien Grall wrote:
>>> 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.
>>
>> Sure.
>>
>>
>> Ian,
>>
>> let's create a /arm/linux.git tree on xenbits where both Julien and I
>> can push. The idea is that we'll try to use vanilla kernel releases but
>> we'll keep it around just in case we'll need special patches for
>> hardware support in the future. If it turns out that we don't actually
>> need it, we can get rid of it in a year or two.
>>
>> We'll initialize /arm/linux.git based on the current linux-arm-xen
>> branch. /arm/linux.git will replace linux-arm-xen in OSSTest.
>>
>> Sounds good?
>
> I don't mind as long as I have access to the arm linux tree. Ian do you
> have any opinions?
>
> Cheers,
>
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-12-05 15:46 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
2017-10-23 21:33 ` Stefano Stabellini
2017-11-02 13:34 ` Julien Grall
2017-12-05 15:46 ` Julien Grall [this message]
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=b82b3feb-720d-d24f-1b49-0aa8f9ff3f6f@linaro.org \
--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=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).