[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2B0E3F215D1AB84DA946C8BEE234CCC9370ECD71@ORSMSX101.amr.corp.intel.com>
Date: Thu, 1 May 2014 14:56:53 +0000
From: "Ertman, DavidX M" <davidx.m.ertman@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Eric Dumazet <eric.dumazet@...il.com>
CC: "stable@...r.kernel.org" <stable@...r.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Request for stable inclusion
> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@...utronix.de]
> Sent: Wednesday, April 30, 2014 1:37 PM
> To: Eric Dumazet
> Cc: Ertman, DavidX M; stable@...r.kernel.org; Kirsher, Jeffrey T;
> netdev@...r.kernel.org
> Subject: RE: Request for stable inclusion
>
> On Wed, 30 Apr 2014, Eric Dumazet wrote:
>
> > On Wed, 2014-04-30 at 19:40 +0000, Ertman, DavidX M wrote:
> >
> > > The commit that caused the issue went into net-next on June 21, 2013.
> So at least 3.11 and forward, and probably 3.10.
> >
> > There is a way to know exactly the cut point :
> >
> > $ git describe --contains da1e2046e5
> > v3.12-rc1~132^2~445^2~6
>
> So 3.12+ is affected.
Yes, sorry about that. I was looking at when it got committed into an internal queue as opposed to taken into Linus's tree. Silly mistake.
Dave Ertman
--
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