mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: William Dauchy <william@gandi.net>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Vrabel <david.vrabel@citrix.com>,
	"Christopher S. Aker" <caker@theshore.net>,
	David Miller <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: xen-netback fixes for stable 35876b5 3e55f8b
Date: Fri, 22 Feb 2013 17:44:28 +0000	[thread overview]
Message-ID: <1361555068.26546.144.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20130222164728.GB27794@gandi.net>

Adding Dave Miller, the networking maintainer. He needs to ack such
requests I think. Adding netdev too for good meassure.

On Fri, 2013-02-22 at 16:47 +0000, William Dauchy wrote:
> Hello,
> 
> I believe the two commits 35876b5 and 3e55f8b could be included in stable tree.
> 35876b5 is related to 4885628 already in the stable tree and fixes a
> possible oops.
> 3e55f8b is fixing another possible oops (see commit messages).

DaveM has these queued for stable already:
http://marc.info/?l=xen-devel&m=136086628711282&w=2

He likes to soak thing in mainline for a bit before forwarding to stable
which is likely why they aren't there yet
http://marc.info/?l=xen-devel&m=136029801624783&w=2

Ian.


  parent reply	other threads:[~2013-02-22 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 16:47 William Dauchy
2013-02-22 17:08 ` Greg Kroah-Hartman
2013-02-22 17:17   ` William Dauchy
2013-02-22 17:28     ` Greg Kroah-Hartman
2013-02-22 17:37       ` William Dauchy
2013-02-22 17:44 ` Ian Campbell [this message]
2013-02-22 17:51   ` William Dauchy
2013-02-22 18:32 ` David Miller

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=1361555068.26546.144.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=ben@decadent.org.uk \
    --cc=caker@theshore.net \
    --cc=davem@davemloft.net \
    --cc=david.vrabel@citrix.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=william@gandi.net \
    /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

all inboxes | Powered by JetHome®