From: Romano Giannetti <romanol@upcomillas.es>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Giridhar Pemmasani <pgiri@yahoo.com>
Subject: Re: ndiswrapper tainting
Date: Fri, 22 Feb 2008 09:39:23 +0100 [thread overview]
Message-ID: <1203669563.14123.1.camel@localhost> (raw)
In-Reply-To: <1203642175.14339.17.camel@dv>
On Thu, 2008-02-21 at 20:02 -0500, Pavel Roskin wrote:
> Hello!
>
> What are the chances that incorrect tainting of ndiswrapper will be
> fixed in 2.6.25?
> Please let's not turn it into another empty discussion.
>
>
Seconded. Please.
--
Sorry for the disclaimer --- ¡I cannot stop it!
--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.
This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.
next prev parent reply other threads:[~2008-02-22 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 1:02 ndiswrapper tainting Pavel Roskin
2008-02-22 8:39 ` Romano Giannetti [this message]
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=1203669563.14123.1.camel@localhost \
--to=romanol@upcomillas.es \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgiri@yahoo.com \
--cc=proski@gnu.org \
--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