|
From: Nicholas K. <xer...@gm...> - 2015-02-28 02:11:20
|
On February 27, 2015 7:45:58 PM EST, Jeff Kirsher <jef...@in...> wrote: >On Fri, 2015-02-27 at 16:25 -0500, Nicholas Krause wrote: >> Thanks Shannon, >> For the advice on there being a newer driver and firmware to test >that >> on before reporting the bug against this driver. I am curious as to >> why this newer code is not up streamed to Linux next yet through. > >Because I still have ~40 patches in my queue for i40e that need to go >upstream to get the upstream driver in sync with our out-of-tree >driver. > >Also Nick, please do not take advantage of me being nice to you and >letting you remain on e1000-devel mailing list, even though you have >been banned on @vger.kernel.org mailing lists. It is clear from your >attempts to help Stefan, you do not know the driver and your "blind >stabs in the dark" to assist, only hinder our abilities to assist >others. Jeff, These seem to be the most likely culprits after reading the code. However there seems to be something else going wrong with the function call in the trace code. Jeff I do understand your busy with the upstream merging of the Intel drivers and was just wondering when the merge would be finished. Furthermore I can try tracing this later during my March Break. I do appreciate you being nice to me and am sorry about making you lose your patience. I am interested in learning about the Intel network drivers and working with them, if would like to give me something to start with. Sorry, Nick :( -- Sent from my Android device with K-9 Mail. Please excuse my brevity. |