From: Mike Galbraith <efault@gmx.de>
To: iseletsk@cloudlinux.com
Cc: fa.linux.kernel@googlegroups.com, linux-kernel@vger.kernel.org,
rusty@rustcorp.com.au, Matthew Garrett <mjg59@srcf.ucam.org>,
Alex Lyashkov <umka@cloudlinux.com>
Subject: Re: [PATCH] Taint kernel when lve module is loaded
Date: Sun, 24 Jun 2012 09:33:11 +0200 [thread overview]
Message-ID: <1340523191.7471.159.camel@marge.simpson.net> (raw)
In-Reply-To: <b770341d-e1e3-4d57-b283-3d8ff92b0d36@googlegroups.com>
On Sat, 2012-06-23 at 08:07 -0700, iseletsk@cloudlinux.com wrote:
> Later on we will have new module that is not GPL released.
Too bad refusing to load conceptually alien modules is incompatible with
pragmatic/practical. A decision to eradicate the things is highly
attractive excepting the "cut off your nose to spite your face" bits
contained therein.
Hohum, live long and prosper (possibly nose free) alien life form.
-Mike
next prev parent reply other threads:[~2012-06-24 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.WTHIDfGYg3w7zn9rxlDshNfnPtI@ifi.uio.no>
2012-06-23 15:07 ` [PATCH] Taint kernel when lve module is loaded iseletsk
2012-06-24 6:39 ` Greg KH
2012-06-24 7:33 ` Mike Galbraith [this message]
[not found] ` <fa.lxvUw3/2JBxq1zvQzI4sJk8pEOQ@ifi.uio.no>
[not found] ` <fa.Fdbx7aeDSXKMF/2ajG0IUf0AAKs@ifi.uio.no>
[not found] ` <fa.TAjdtaR/BMl+PZAWwtAit9BevAo@ifi.uio.no>
[not found] ` <fa.cm6Pl6ITE2qRnrdz/DXqaOSgExs@ifi.uio.no>
2012-06-23 19:26 ` iseletsk
2012-06-24 6:35 ` Greg KH
[not found] ` <CA+-XxSG8mpERvUwKgG4M8=ZuSd3P+ZYfw5mL3R4zLTAYGPW3Mw@mail.gmail.com>
2012-07-11 15:26 ` Greg KH
2012-06-22 17:49 Matthew Garrett
2012-06-22 18:43 ` Greg KH
2012-06-22 18:51 ` Matthew Garrett
2012-06-22 19:22 ` Greg KH
2012-06-22 19:43 ` Greg KH
2012-06-22 19:09 ` richard -rw- weinberger
2012-06-22 19:40 ` Greg KH
2012-06-23 0:00 ` Rusty Russell
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=1340523191.7471.159.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=fa.linux.kernel@googlegroups.com \
--cc=iseletsk@cloudlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rusty@rustcorp.com.au \
--cc=umka@cloudlinux.com \
/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