[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1370267454.24512.7.camel@zakaz.uk.xensource.com>
Date: Mon, 3 Jun 2013 14:50:54 +0100
From: Ian Campbell <Ian.Campbell@...rix.com>
To: William Dauchy <wdauchy@...il.com>
CC: Wei Liu <wei.liu2@...rix.com>,
Luis Henriques <luis.henriques@...onical.com>,
<netdev@...r.kernel.org>, <stable@...r.kernel.org>,
xen-devel <xen-devel@...ts.xen.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [Xen-devel] xen-netback stable backports request (regression
fixes)
On Fri, 2013-05-31 at 15:45 +0200, William Dauchy wrote:
> On Fri, May 31, 2013 at 3:20 PM, William Dauchy <wdauchy@...il.com> wrote:
> > I applied the patches on a 3.4.x kernel.
> > for netback I had to include:
> > 9eaee8b xen-netback: fix sparse warning
> > which I guess is ok to include in 3.4
> >
> > for netfront, as Luis said, I also add to include:
> > f36c374 xen/netfront: handle compound page fragments on transmit
> > which is not a simple patch.
>
> at the end, it is not really clever to include f36c374 in 3.4.x since
> 6a8ed46 xen: netback: handle compound page fragments on transmit.
> is not present in netback for 3.4.x
Right, that would be my thinking too, although the patch should be
"harmless" (i.e. it should work fine with non-compound frags) its not
totally trivial so unless the backport of f36c374 is made especially
hard without it its likely not worth the risk.
> at least the netback part is ok for me.
Thanks,
Ian.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists