From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <gregkh@linuxfoundation.org>, Michael Tokarev <mjt@tls.msk.ru>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Alex Lyashkov <umka@cloudlinux.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: lve module taint?
Date: Thu, 20 Sep 2012 08:29:02 +0930 [thread overview]
Message-ID: <877grppqkp.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120919071942.GF16905@kroah.com>
Greg KH <gregkh@linuxfoundation.org> writes:
> On Wed, Sep 19, 2012 at 09:58:09AM +0400, Michael Tokarev wrote:
>> On 19.09.2012 06:02, Rusty Russell wrote:
>> This is setting a, in my opinion, rather bad precedent. Next we'll
>> be adding various modules here due to various reasons.
We have, that bridge has already been crossed. I wasn't asking about
the patch itself.
My question was simply whether the lve module is still claiming to be
GPL without being compliant or not.
Cheers,
Rusty.
prev parent reply other threads:[~2012-09-20 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 2:02 lve module taint? Rusty Russell
2012-09-19 5:58 ` Michael Tokarev
2012-09-19 7:19 ` Greg KH
2012-09-19 22:59 ` Rusty Russell [this message]
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=877grppqkp.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.