From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall 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 Message-ID: <55102F8C.6050509@linaro.org> References: <1426802044-19444-1-git-send-email-boris.ostrovsky@oracle.com> <55100A26.7080801@linaro.org> <551031B0020000780006C984@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap , Jan Beulich Cc: elena.ufimtseva@oracle.com, Wei Liu , Ian Campbell , Stefano Stabellini , Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Keir Fraser , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 23/03/15 14:38, George Dunlap wrote: > On Mon, Mar 23, 2015 at 2:30 PM, Jan Beulich wrote: >>>>> On 23.03.15 at 13:42, 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