xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: George Dunlap <dunlapg@umich.edu>
Cc: Olaf Hering <olaf@aepfle.de>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New 4.0.2 and 4.1.1 release candidates
Date: Thu, 26 May 2011 10:09:20 +0100	[thread overview]
Message-ID: <CA03D750.2DAB7%keir@xen.org> (raw)
In-Reply-To: <BANLkTinjNmKy+oQr7JEgq+G03LqzEeA06g@mail.gmail.com>

On 26/05/2011 09:36, "George Dunlap" <dunlapg@umich.edu> wrote:

> On Tue, May 24, 2011 at 6:58 PM, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 24/05/2011 17:13, "Olaf Hering" <olaf@aepfle.de> wrote:
>> 
>>> On Sat, May 21, Keir Fraser wrote:
>>> 
>>>> Tag '4.1.1-rc1' in http://xenbits.xen.org/staging/xen-4.1-testing.hg
>>>>  - Please test, and also suggest further backports for 4.1.1.
>>> 
>>> Keir,
>>> 
>>> what about all the changes made to xen/common/trace.c up to now?
>> 
>> 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.
> 
> 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 in
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

      reply	other threads:[~2011-05-26  9:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21  7:04 New 4.0.2 and 4.1.1 release candidates Keir Fraser
2011-05-24  7:24 ` Keir Fraser
2011-05-24 14:17   ` W. Michael Petullo
2011-05-05 17:15     ` Proposal: vif-local W. Michael Petullo
2011-05-06  8:42       ` Ian Campbell
2011-05-06 17:06         ` W. Michael Petullo
2011-05-09  8:45           ` Ian Campbell
2011-05-09 17:10             ` W. Michael Petullo
2011-05-10  8:02               ` Ian Campbell
2011-05-10 16:06                 ` W. Michael Petullo
2011-05-10 16:12                   ` Ian Campbell
2011-05-24 17:31                 ` Proposal: vif-local [and 1 more messages] Ian Jackson
2011-05-24 17:51                   ` Ian Campbell
2011-05-25  9:45                     ` Ian Jackson
2011-05-24 15:49     ` Re: New 4.0.2 and 4.1.1 release candidates Keir Fraser
2011-05-24 16:13 ` Olaf Hering
2011-05-24 17:58   ` Keir Fraser
2011-05-24 18:25     ` Olaf Hering
2011-05-24 20:04       ` Keir Fraser
2011-05-26  8:36     ` George Dunlap
2011-05-26  9:09       ` Keir Fraser [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=CA03D750.2DAB7%keir@xen.org \
    --to=keir@xen.org \
    --cc=dunlapg@umich.edu \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.com \
    /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).