do not express your frustration ...
wasn't frustration but rather playful sarcasm.
This was not a bug report at all...
Wasn't really meant to be a true blue bug report (my bad I guess). Anywho, I
know you guys have big fish to fry so I tried to keep it short and to the
point. I knew something
In SMP kernels 2.6.21 and prior you could use a SOCK's sendmsg() call via the
PROTO structure directly. e.g., sock-sk_prot-sendmsg().
Now in 2.6.22 and later kernels you must use the higher level SOCKET to make a
call to PROTO_OPS then to sendmsg(). e.g., socket-ops-sendmsg().
Would someone
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. ;-}
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
Kevin Wilson wrote:
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
Hi Kevin.
On Thu, Dec 13, 2007 at 04:00:02PM -0600, Kevin Wilson ([EMAIL PROTECTED])
wrote:
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
