[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141101.134142.888127846627939710.davem@davemloft.net>
Date: Sat, 01 Nov 2014 13:41:42 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: cwang@...pensource.com
Cc: ben@...adent.org.uk, vlee@...pensource.com, amirv@...lanox.com,
ogerlitz@...lanox.com, jackm@....mellanox.co.il,
eugenia@...lanox.com, matanb@...lanox.com, netdev@...r.kernel.org
Subject: Re: [stable request <= 3.11] net/mlx4_en: Fix BlueFlame race
From: Cong Wang <cwang@...pensource.com>
Date: Sat, 1 Nov 2014 10:17:43 -0700
> On Fri, Oct 31, 2014 at 6:29 PM, Ben Hutchings <ben@...adent.org.uk> wrote:
>> On Sat, 2014-10-18 at 14:14 -0700, Vinson Lee wrote:
>>> Hi.
>>>
>>> Please consider backporting upstream commit
>>> 2d4b646613d6b12175b017aca18113945af1faf3 "net/mlx4_en: Fix BlueFlame
>>> race" to stable kernels <= 3.11.
>>>
>>> commit 2d4b646613d6b12175b017aca18113945af1faf3
>>> Author: Eugenia Emantayev <eugenia@...lanox.com>
>>> Date: Thu Jul 25 19:21:23 2013 +0300
>>>
>>> net/mlx4_en: Fix BlueFlame race
>> [...]
>>
>> David doesn't support anything older than 3.12 now, so you should send
>> requests for older stable branches directly to the stable list.
>
> Interesting, is there a document saying which stable kernels netdev
> supports? and how are they chosen?
>
> I thought netdev supports all -stable maintainers support.
>
> Anyway, we will send the request directly to Greg then.
There is no documented way nor do I wish to state anything so strictly.
I want maximum flexibility for such a time consuming task.
I tend to go back 3 or 4 releases at most, and it really depends upon
the difficulty of the backports and my own time constraints.
--
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