From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Lars Kurth" <lars.kurth@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wei.liu2@citrix.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 11:56:01 -0400 [thread overview]
Message-ID: <20171020155601.GF17369@char.us.oracle.com> (raw)
In-Reply-To: <23018.2432.369307.794318@mariner.uk.xensource.com>
On Fri, Oct 20, 2017 at 03:34:40PM +0100, Ian Jackson wrote:
> Currently we are running our ARM tests in osstest off a branch in
> Stefano's personal Linux tree. This is a bit unsatisfactory.
>
> We would like to switch to a branch that Julien can push to too, and
> that is in a more official place.
>
> There are two options:
>
> 1. Create an ARM-specific Xen tree. Currently we don't have many
> ARM-specific trees but I don't see a problem with this. So
> we could create
> /arm/linux.git
> on xenbits.
>
> 2. Use a branch name within /linux-pvops.git, the main Linux
> tree on xenbits. This would mean making Julien a committer.
3. Use upstream released kernels. Follow them when they are released.
>
> What do people think would be best ?
>
> Also, separately, surely Julien should be listed in MAINTAINERS for
> the Xen ARM stuff in upstream Linux ? He doesn't seem to be at least
> in the version I have lying about here...
>
> Thanks,
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-20 15:56 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 [this message]
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
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=20171020155601.GF17369@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.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).