From: David Miller <davem@davemloft.net>
To: Kevin.Wilson@comtrol.com
Cc: netdev@vger.kernel.org
Subject: Re: What was the reason for 2.6.22 SMP kernels to change how sendmsg is called?
Date: Thu, 13 Dec 2007 13:17:53 -0800 (PST) [thread overview]
Message-ID: <20071213.131753.156591181.davem@davemloft.net> (raw)
In-Reply-To: <B1F576FE19C55C43B8D2E31F061B50C04E60B1@exchange.comtrol.com>
From: "Kevin Wilson" <Kevin.Wilson@comtrol.com>
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.
next prev parent reply other threads:[~2007-12-13 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 20:54 What was the reason for 2.6.22 SMP kernels to change how sendmsg is called? Kevin Wilson
2007-12-13 21:17 ` David Miller [this message]
2007-12-13 22:00 ` Kevin Wilson
2007-12-14 0:45 ` Brandeburg, Jesse
2007-12-14 6:33 ` Evgeniy Polyakov
2007-12-14 17:55 ` Kevin Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071213.131753.156591181.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Kevin.Wilson@comtrol.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).