Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Ian.Campbell@citrix.com
Cc: xen-devel@lists.xen.org, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: xen-netback stable backport requests
Date: Sat, 09 Nov 2013 15:56:13 -0500 (EST)	[thread overview]
Message-ID: <20131109.155613.787148078862725586.davem@davemloft.net> (raw)
In-Reply-To: <1383826530.32399.13.camel@kazak.uk.xensource.com>

From: Ian Campbell <Ian.Campbell@citrix.com>
Date: Thu, 7 Nov 2013 12:15:30 +0000

> 279f438e36c0 "xen-netback: Don't destroy the netdev until the vif is
> shut down" has hit stable but unfortunately is causing regressions. 
> 
> This should be fixed by dc62ccaccfb1 "xen-netback: transition to CLOSED
> when removing a VIF" which depends on ea732dff5cfa "xen-netback: Handle
> backend state transitions in a more robust way".
> 
> Please could you queue hose two for stable.

Queued up for 3.10 and 3.11 -stable, thanks!

      reply	other threads:[~2013-11-09 20:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 12:15 xen-netback stable backport requests Ian Campbell
2013-11-09 20:56 ` David Miller [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=20131109.155613.787148078862725586.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox