[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB3PR0402MB3849850266808EC52F88A783ECE90@DB3PR0402MB3849.eurprd04.prod.outlook.com>
Date: Wed, 17 Jan 2018 14:15:51 +0000
From: Madalin-cristian Bucur <madalin.bucur@....com>
To: Andrew Lunn <andrew@...n.ch>,
Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
CC: "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"madskateman@...il.com" <madskateman@...il.com>,
"David S . Miller" <davem@...emloft.net>
Subject: RE: DPAA Ethernet traffice troubles with Linux kernel
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@...n.ch]
> Sent: Wednesday, January 17, 2018 3:44 PM
> To: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
> Subject: Re: DPAA Ethernet traffice troubles with Linux kernel
>
> > That doesn't work really, having users to hit the bug, debug it, fix it
> and then
> > find it fixed already in upstream, then specifically request it to be
> backported to stable.
> > I don't need this fix to be backported, already got it. Someone else
> might though.
>
> The "someone else might though" is a big point of asking for it to
> added to stable. The other reason is it means one less patch you need
> to maintain in your build.
I've sent that patch [1] for net but I guess the timing was wrong and
it was merged to net-next.
> > I would be interested in bug fixes upstream which fixes:
>
> Did you try upstream? Does it give the same errors?
>
> Andrew
[1] https://patchwork.kernel.org/patch/10146119/
Madalin
Powered by blists - more mailing lists