From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: New 4.0.2 and 4.1.1 release candidates Date: Thu, 26 May 2011 10:09:20 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap Cc: Olaf Hering , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 26/05/2011 09:36, "George Dunlap" wrote: > On Tue, May 24, 2011 at 6:58 PM, Keir Fraser wrote: >> On 24/05/2011 17:13, "Olaf Hering" wrote: >>=20 >>> On Sat, May 21, Keir Fraser wrote: >>>=20 >>>> Tag '4.1.1-rc1' in http://xenbits.xen.org/staging/xen-4.1-testing.hg >>>> =A0- Please test, and also suggest further backports for 4.1.1. >>>=20 >>> Keir, >>>=20 >>> what about all the changes made to xen/common/trace.c up to now? >>=20 >> There are *loads* of them. I don't think so, presumably it's not really = all >> bug fixes. It's somewhat up to George however. >=20 > It looks like 23091:67632e5cf652 and 23128:4a335f1000ea are fixes to > code changed in 23050:4ebba54b666f, is that correct? I don't see > anything else that's a candidate for backporting. Yes, my understanding is that all subsequent changes and fixes to trace.c i= n xen-unstable stem from c/s 23050, which is a big feature patch likely unsuitable for backport to 4.1. So we should put this to bed and backport nothing. -- Keir > -George