linux-kernel - Re: [PATCH] net: macb: Handle the RXUBR interrupt on all devices

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20150511.102815.1978586728654404293.davem@davemloft.net>
Date:	Mon, 11 May 2015 10:28:15 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	nicolas.ferre@...el.com
Cc:	nathan.sullivan@...com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: macb: Handle the RXUBR interrupt on all devices

From: Nicolas Ferre <nicolas.ferre@...el.com>
Date: Mon, 11 May 2015 12:10:54 +0200

> Le 09/05/2015 22:04, David Miller a écrit :
>> From: Nathan Sullivan <nathan.sullivan@...com>
>> Date: Tue, 5 May 2015 15:00:25 -0500
>> 
>>> The same hardware issue the at91 must work around applies to at least the
>>> Zynq ethernet, and possibly more devices.  The driver also needs to handle
>>> the RXUBR interrupt since it turns it on with MACB_RX_INT_FLAGS anyway.
>>>
>>> Signed-off-by: Nathan Sullivan <nathan.sullivan@...com>
>> 
>> Applied, thank you.
> 
> A v2 of this patch with more explanation in both the commit message and
> in code comments had been sent. Not a big deal (I suspect you can't use
> the v2 one, now that it's applied in your tree, can you?).

Sorry, yes I see there was a v2.  If you want to send me a relative patch that
corrects things, I can apply that.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/