From: Julien Grall <julien.grall@linaro.org>
To: George Dunlap <dunlapg@umich.edu>, Jan Beulich <JBeulich@suse.com>
Cc: elena.ufimtseva@oracle.com, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Keir Fraser <keir@xen.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v5 0/8] Display IO topology when PXM data is available (plus some cleanup)
Date: Mon, 23 Mar 2015 15:21:48 +0000 [thread overview]
Message-ID: <55102F8C.6050509@linaro.org> (raw)
In-Reply-To: <CAFLBxZZ5JWYGBRJ4Vvj4VC7y8bf8GqqvsLrjPgGtfwyiLHg2=A@mail.gmail.com>
On 23/03/15 14:38, George Dunlap wrote:
> On Mon, Mar 23, 2015 at 2:30 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>>>> On 23.03.15 at 13:42, <julien.grall@linaro.org> wrote:
>>> It would be nice to at least build test it ARM/ARM64 before pushing
>>> patches which modify common code.
>>
>> I try to remember that, but do not always succeed. Really I'd expect
>> people to not even submit such patches.
>
> To be fair, this is the reason we have a push gate; people who want
> only non-broken builds should use master rather than staging.
I'm using staging because it often contains bug fixes which is necessary
for booting Xen on my boards.
Using master means having least a week old Xen and cherry-pick some
patches from staging.
The latter may be difficult when the patch has dependency.
> But given how long the test cycles take, it would be better if people
> submitting patches did some smoke-testing first.
I think it's a good solution, building Xen ARM take less than 2 minutes
Cheers,
--
Julien Grall
prev parent reply other threads:[~2015-03-23 15:21 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 21:53 [PATCH v5 0/8] Display IO topology when PXM data is available (plus some cleanup) Boris Ostrovsky
2015-03-19 21:53 ` [PATCH v5 1/8] numa: __node_distance() should return u8 Boris Ostrovsky
2015-03-20 14:25 ` Konrad Rzeszutek Wilk
2015-03-19 21:53 ` [PATCH v5 2/8] pci: Stash device's PXM information in struct pci_dev Boris Ostrovsky
2015-03-20 14:01 ` Konrad Rzeszutek Wilk
2015-03-19 21:53 ` [PATCH v5 3/8] sysctl: Make XEN_SYSCTL_topologyinfo sysctl a little more efficient Boris Ostrovsky
2015-03-20 13:25 ` Ian Campbell
2015-03-20 14:00 ` Boris Ostrovsky
2015-03-20 14:10 ` Ian Campbell
2015-03-25 16:13 ` Andrew Cooper
2015-03-19 21:54 ` [PATCH v5 4/8] sysctl: Make XEN_SYSCTL_numainfo " Boris Ostrovsky
2015-03-20 13:26 ` Ian Campbell
2015-03-20 16:15 ` Jan Beulich
2015-03-19 21:54 ` [PATCH v5 5/8] sysctl: Add sysctl interface for querying PCI topology Boris Ostrovsky
2015-03-20 14:21 ` Konrad Rzeszutek Wilk
2015-03-20 16:26 ` Jan Beulich
2015-03-20 20:01 ` Boris Ostrovsky
2015-03-23 8:15 ` Jan Beulich
2015-03-23 13:58 ` Boris Ostrovsky
2015-03-19 21:54 ` [PATCH v5 6/8] libxl/libxc: Move libxl_get_cpu_topology()'s hypercall buffer management to libxc Boris Ostrovsky
2015-03-20 13:54 ` Ian Campbell
2015-03-20 14:24 ` Boris Ostrovsky
2015-03-20 14:30 ` Ian Campbell
2015-03-19 21:54 ` [PATCH v5 7/8] libxl/libxc: Move libxl_get_numainfo()'s " Boris Ostrovsky
2015-03-20 13:49 ` Konrad Rzeszutek Wilk
2015-03-20 14:10 ` Boris Ostrovsky
2015-03-20 14:21 ` Ian Campbell
2015-03-20 13:56 ` Ian Campbell
2015-03-20 14:31 ` Boris Ostrovsky
2015-03-20 14:46 ` Ian Campbell
2015-03-20 14:59 ` Boris Ostrovsky
2015-03-19 21:54 ` [PATCH v5 8/8] libxl: Add interface for querying hypervisor about PCI topology Boris Ostrovsky
2015-03-23 12:42 ` [PATCH v5 0/8] Display IO topology when PXM data is available (plus some cleanup) Julien Grall
2015-03-23 13:47 ` Boris Ostrovsky
2015-03-23 14:30 ` George Dunlap
2015-03-23 14:33 ` Boris Ostrovsky
2015-03-23 14:42 ` Ian Campbell
2015-03-23 15:26 ` Julien Grall
2015-03-23 15:27 ` Jan Beulich
2015-03-23 15:33 ` Boris Ostrovsky
2015-03-23 15:46 ` Jan Beulich
2015-03-23 14:30 ` Jan Beulich
2015-03-23 14:38 ` George Dunlap
2015-03-23 15:17 ` Ian Campbell
2015-03-23 15:21 ` Julien Grall [this message]
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=55102F8C.6050509@linaro.org \
--to=julien.grall@linaro.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=dunlapg@umich.edu \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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.