netdev - Re: [PATCH net-next v1] net: netcp: remove call to netif_carrier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <553E7B64.3080407@ti.com>
Date:	Mon, 27 Apr 2015 14:09:40 -0400
From:	Murali Karicheri <m-karicheri2@...com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v1] net: netcp: remove call to netif_carrier_(on/off)
 for MAC to Phy interface

On 04/27/2015 01:23 PM, David Miller wrote:
> From: Murali Karicheri<m-karicheri2@...com>
> Date: Mon, 27 Apr 2015 13:07:35 -0400
>
>> On 04/25/2015 03:48 PM, David Miller wrote:
>>> From: Murali Karicheri<m-karicheri2@...com>
>>> Date: Fri, 24 Apr 2015 15:01:41 -0400
>>>
>>>> Currently when interface type is MAC to Phy, netif_carrier_(on/off)
>>>> is called which is not needed as Phy lib already updates the carrier
>>>> status to net stack. This is needed only for other interface types
>>>>
>>>> Signed-off-by: Murali Karicheri<m-karicheri2@...com>
>>>
>>> net-next is not open for submissions yet
>> David,
>>
>> Do I need to re-submit this patch when the net-next gets opened for
>> this? This is essentially a bug fix and can be applied to current
>
> If it's really a bug fix, then you shouldn't target it at net-next.
>
> I'll never understand why people do things like this.
Ok. My bad. I will re-send it with proper prefix for applying to v4.1.

-- 
Murali Karicheri
Linux Kernel, Texas Instruments
--
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