From: Pavel Roskin <proski@gnu.org>
To: linux-kernel@vger.kernel.org
Cc: Jon Masters <jonathan@jonmasters.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Giridhar Pemmasani <pgiri@yahoo.com>
Subject: ndiswrapper tainting
Date: Thu, 21 Feb 2008 20:02:55 -0500 [thread overview]
Message-ID: <1203642175.14339.17.camel@dv> (raw)
Hello!
What are the chances that incorrect tainting of ndiswrapper will be
fixed in 2.6.25? I'm worried that it still hasn't happened in the
mainline repository. It's unfortunate to see that a long discussion
didn't result in a simple fix. If anyone is waiting for my patch,
please let me know what kind of patch I'm supposed to submit and to
which address.
If the problem is not fixed in 2.6.25, the ndiswrapper module will need
to be renamed in the next release, because otherwise the problem with
unresolved symbols will quickly become the number one in the FAQ. But
this is undesirable because it would break existing modprobe
configuration files that bind ndiswrapper to specific devices.
Please let's not turn it into another empty discussion.
I represent only myself and I'm not a lawyer.
--
Regards,
Pavel Roskin
next reply other threads:[~2008-02-22 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 1:02 Pavel Roskin [this message]
2008-02-22 8:39 ` ndiswrapper tainting Romano Giannetti
2008-02-22 9:42 ` Alan Cox
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=1203642175.14339.17.camel@dv \
--to=proski@gnu.org \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgiri@yahoo.com \
--cc=rusty@rustcorp.com.au \
/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