From: Greg KH <gregkh@linuxfoundation.org>
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: Sat, 23 Jun 2012 23:39:03 -0700 [thread overview]
Message-ID: <20120624063903.GB11266@kroah.com> (raw)
In-Reply-To: <b770341d-e1e3-4d57-b283-3d8ff92b0d36@googlegroups.com>
On Sat, Jun 23, 2012 at 08:07:12AM -0700, iseletsk@cloudlinux.com wrote:
> Hello Everyone,
>
> I am very sorry about this situation. It was my oversight. We planned
> to close source the module, and we will do it later on. Yet, it looks
> like one of our developers missed the point -- and did things
> incorrectly.
>
> Please, give us two-three weeks to straighten things out. By the end
> of three weeks I plan to have source RPMs with the GPLed version of
> the modules available in our source repositories.
As you built the binary from some codebase already, why not just post
the source for this code now? There should not be any delay needed.
> Later on we will have new module that is not GPL released.
Why? What is that going to provide to you? You are aware of how the
Linux kernel community feels about closed source kernel modules, and how
your customers will be the ones dealing with the problems surrounding
that type of decision?
> Once again -- I am sorry about the incident. We haven't planned to
> deceive anyone. This was more of an internal miscommunication then
> anything else.
Understood about the miscommunication, but I don't understand any delay
as you do kind of have to provide the source now that we have asked for
it as per the license you released it to us.
thanks,
greg k-h
next prev parent reply other threads:[~2012-06-24 6:39 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 [this message]
2012-06-24 7:33 ` Mike Galbraith
[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=20120624063903.GB11266@kroah.com \
--to=gregkh@linuxfoundation.org \
--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