I see your point but it just so happens it is a GPL'd driver, as is all of our Linux code we produce for our hardware. Granted it is out of tree, and after you saw it you would want it to stay that way. However, I would have sent you the whole thing if that is a pre-req to cordial exchanges on this list.
Nonetheless, a somewhat recent change in your tree, that I could not pinpoint on my own, caused the driver to stop functioning properly. So after much searching in git/google/sources with no luck, I decided to ask for a little assistance, maybe just a hint as to where the culprit may be in the tree so I could investigate for myself. For SNGs I tried the method that now works but I am still at a loss as to (can't find) what changes in the tree caused it to fail. Does that now clarify/help matters any? Regards, Kevin -----Original Message----- From: David Miller [mailto:[EMAIL PROTECTED] Sent: Thursday, December 13, 2007 15:18 To: Kevin Wilson Cc: netdev@vger.kernel.org Subject: Re: What was the reason for 2.6.22 SMP kernels to change how sendmsg is called? From: "Kevin Wilson" <[EMAIL PROTECTED]> Date: Thu, 13 Dec 2007 14:54:31 -0600 > The 2nd method fixes the kernel oops I reported. Thanks to all those > that assisted me (0) with my first post to this list (see below) > ... uh, oh yeah, did I mention that number would tally up to ZERO > people. ;-} Because the knowledgable folks here have zero interest in helping people with out-of-tree-likely-binary-only modules, because in such cases you have our code but we don't have your's. Have a nice day. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
