Re: Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-07 Thread Mario Molitor
, June 6, 2017 7:43 AM To: Mario Molitor ; alexandre.tor...@st.com Cc: net...@vger.kernel.org ; linux-kernel@vger.kernel.org Subject: Re: Stmmac: fix for hw timestamp of GMAC 3 unit Hi Mario thanks for your tests, and, at first glance, your patches seem to be sensible so, please, send the changes

Re: Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-07 Thread Mario Molitor
, June 6, 2017 7:43 AM To: Mario Molitor ; alexandre.tor...@st.com Cc: net...@vger.kernel.org ; linux-kernel@vger.kernel.org Subject: Re: Stmmac: fix for hw timestamp of GMAC 3 unit Hi Mario thanks for your tests, and, at first glance, your patches seem to be sensible so, please, send the changes

Re: Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-05 Thread Giuseppe CAVALLARO
Hi Mario thanks for your tests, and, at first glance, your patches seem to be sensible so, please, send the changes as patches for net.git kernel. Regards Peppe On 6/6/2017 12:11 AM, Mario Molitor wrote: Dear stmmac maintainer group, I have found an problem in stmmac driver of linux

Re: Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-05 Thread Giuseppe CAVALLARO
Hi Mario thanks for your tests, and, at first glance, your patches seem to be sensible so, please, send the changes as patches for net.git kernel. Regards Peppe On 6/6/2017 12:11 AM, Mario Molitor wrote: Dear stmmac maintainer group, I have found an problem in stmmac driver of linux

Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-05 Thread Mario Molitor
Dear stmmac maintainer group, I have found an problem in stmmac driver of linux kernel and I hope for a fix in the mainline kernel. At the moment I have two patch files which fix this problem for me. The problem seems created with the commit d2042052a0aa6a54f01a0c9e14243ec040b100e2 and

Stmmac: fix for hw timestamp of GMAC 3 unit

2017-06-05 Thread Mario Molitor
Dear stmmac maintainer group, I have found an problem in stmmac driver of linux kernel and I hope for a fix in the mainline kernel. At the moment I have two patch files which fix this problem for me. The problem seems created with the commit d2042052a0aa6a54f01a0c9e14243ec040b100e2 and