[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160918.220046.1374771296032853447.davem@davemloft.net>
Date: Sun, 18 Sep 2016 22:00:46 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: ttoukan.linux@...il.com
Cc: tariqt@...lanox.com, netdev@...r.kernel.org, eranbe@...lanox.com
Subject: Re: [PATCH net-next 0/5] mlx4 misc fixes and improvements
From: Tariq Toukan <ttoukan.linux@...il.com>
Date: Sun, 18 Sep 2016 10:27:23 +0300
> Hi Dave,
>
> On 16/09/2016 2:21 AM, David Miller wrote:
>> From: Tariq Toukan <tariqt@...lanox.com>
>> Date: Mon, 12 Sep 2016 16:20:11 +0300
>>
>>> This patchset contains some bug fixes, a cleanup, and small
>>> improvements
>>> from the team to the mlx4 Eth and core drivers.
>>>
>>> Series generated against net-next commit:
>>> 02154927c115 "net: dsa: bcm_sf2: Get VLAN_PORT_MASK from b53_device"
>>>
>>> Please push the following patch to -stable >= 4.6 as well:
>>> "net/mlx4_core: Fix to clean devlink resources"
>> Again, coding style fixes and optimizations like branch prediction
>> hints are not bug fixes and therefore not appropriate for 'net'.
> Yes, I know. Please notice that it was submitted to net-next this
> time.
This is completely incompatible with a request for one of the changes
to go into -stable.
If the change is not in 'net', it can't go to -stable.
Powered by blists - more mailing lists