Hello Sasha,
Were you able to reproduce this issue?
Do you have a patch fixing the close function inconsistencies that you
mentioned which I could try out?
Thanks,
Tyler
On 11/21/2016 1:40 PM, Baicar, Tyler wrote:
On 11/17/2016 6:31 AM, Neftin, Sasha wrote:
On 11/13/2016 10:34 AM, Neftin
On 11/17/2016 6:31 AM, Neftin, Sasha wrote:
On 11/13/2016 10:34 AM, Neftin, Sasha wrote:
On 11/11/2016 12:35 AM, Baicar, Tyler wrote:
Hello Sasha,
On 11/9/2016 11:19 PM, Neftin, Sasha wrote:
On 11/9/2016 11:41 PM, Tyler Baicar wrote:
Move IRQ free code so that it will happen regardless of
On 11/13/2016 2:25 AM, Neftin, Sasha wrote:
On 11/13/2016 10:34 AM, Neftin, Sasha wrote:
On 11/11/2016 12:35 AM, Baicar, Tyler wrote:
Hello Sasha,
On 11/9/2016 11:19 PM, Neftin, Sasha wrote:
On 11/9/2016 11:41 PM, Tyler Baicar wrote:
Move IRQ free code so that it will happen regardless of
Hello Sasha,
On 11/9/2016 11:19 PM, Neftin, Sasha wrote:
On 11/9/2016 11:41 PM, Tyler Baicar wrote:
Move IRQ free code so that it will happen regardless of the
__E1000_DOWN bit. Currently the e1000e driver only releases its IRQ
if the __E1000_DOWN bit is cleared. This is not sufficient because
On 11/3/2016 2:09 AM, Ruinskiy, Dima wrote:
-Original Message-
From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
Behalf Of Tyler Baicar
Sent: Wednesday, 02 November, 2016 23:08
To: Kirsher, Jeffrey T; intel-wired-...@lists.osuosl.org;
netdev@vger.kernel.org; linux
