All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org,
	stefano.stabellini@eu.citrix.com,
	"xen.org" <ian.jackson@eu.citrix.com>,
	Paul Durrant <paul.durrant@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [linux-3.10 bisection] complete test-amd64-i386-qemut-rhel6hvm-intel
Date: Thu, 7 Nov 2013 12:22:54 +0000	[thread overview]
Message-ID: <1383826974.32399.15.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <527B84A2.3060806@citrix.com>

On Thu, 2013-11-07 at 12:16 +0000, David Vrabel wrote:
> On 07/11/13 12:16, Ian Campbell wrote:
> > On Thu, 2013-11-07 at 12:12 +0000, Ian Campbell wrote:
> >> On Thu, 2013-11-07 at 12:07 +0000, David Vrabel wrote:
> > 
> >>> The 3.10 stable tree is missing dc62ccaccfb139d9b04bbc5a2688a4402adbfab3
> >>> (xen-netback: transition to CLOSED when removing a VIF) which fixes a
> >>> regression introduced in the above patch.
> >>>
> >>> This depends on ea732dff5cfa10789007bf4a5b935388a0bb2a8f (xen-netback:
> >>> Handle backend state transitions in a more robust way) which fixes an
> >>> issue with some old Windows frontends.
> >>>
> >>> Both of these should be backported to stable.
> >>
> >> Yes, this was also discussed yesterday in reply to one of the failures.
> >> Has someone pinged DaveM already?
> > 
> > Nevermind, I just did it...
> 
> As did I...

Oops, oh well, he'll certainly get the message ;-)

Ian.

  reply	other threads:[~2013-11-07 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  4:04 [linux-3.10 bisection] complete test-amd64-i386-qemut-rhel6hvm-intel xen.org
2013-11-07 12:07 ` David Vrabel
2013-11-07 12:12   ` Ian Campbell
2013-11-07 12:16     ` Ian Campbell
2013-11-07 12:16       ` David Vrabel
2013-11-07 12:22         ` Ian Campbell [this message]
2015-01-24 21:55 xen.org

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=1383826974.32399.15.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=paul.durrant@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --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 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.