From: David Miller <davem@davemloft.net>
To: cwang@twopensource.com
Cc: ben@decadent.org.uk, vlee@twopensource.com, amirv@mellanox.com,
ogerlitz@mellanox.com, jackm@dev.mellanox.co.il,
eugenia@mellanox.com, matanb@mellanox.com,
netdev@vger.kernel.org
Subject: Re: [stable request <= 3.11] net/mlx4_en: Fix BlueFlame race
Date: Sat, 01 Nov 2014 13:41:42 -0400 (EDT) [thread overview]
Message-ID: <20141101.134142.888127846627939710.davem@davemloft.net> (raw)
In-Reply-To: <CAHA+R7OyLv2YO8AduNhnEgW3RyYZwWNEHY6W-v_HXgVT9AOaKw@mail.gmail.com>
From: Cong Wang <cwang@twopensource.com>
Date: Sat, 1 Nov 2014 10:17:43 -0700
> On Fri, Oct 31, 2014 at 6:29 PM, Ben Hutchings <ben@decadent.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@mellanox.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.
next prev parent reply other threads:[~2014-11-01 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 21:14 [stable request <= 3.11] net/mlx4_en: Fix BlueFlame race Vinson Lee
2014-10-21 23:15 ` Cong Wang
2014-10-22 4:17 ` Or Gerlitz
2014-10-22 11:15 ` Amir Vadai
2014-11-01 1:29 ` Ben Hutchings
2014-11-01 17:17 ` Cong Wang
2014-11-01 17:41 ` David Miller [this message]
2014-11-03 17:22 ` Cong Wang
2014-11-03 20:09 ` David Miller
2014-11-05 19:38 ` Vinson Lee
2014-11-19 1:44 ` Greg KH
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=20141101.134142.888127846627939710.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=ben@decadent.org.uk \
--cc=cwang@twopensource.com \
--cc=eugenia@mellanox.com \
--cc=jackm@dev.mellanox.co.il \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=vlee@twopensource.com \
/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;
as well as URLs for NNTP newsgroup(s).