ndiswrapper tainting

[Pavel Roskin]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/