public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Johnston <dj@deadhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
	tytso@mit.edu, richard.weinberger@gmail.com,
	linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: Why is my copyright code in the linux kernel?
Date: Thu, 03 Mar 2011 21:29:44 -0800	[thread overview]
Message-ID: <4D7078C8.8050009@deadhat.com> (raw)
In-Reply-To: <4D6EBC04.5050709@zytor.com>

On 3/2/2011 1:52 PM, H. Peter Anvin wrote:
> On 03/01/2011 03:54 PM, Ted Ts'o wrote:
>> On Wed, Mar 02, 2011 at 12:30:45AM +0100, richard -rw- weinberger wrote:
>>>> You will see a remarkable resemblance to parts of
>>>> linux-2.6.36.2/drivers/staging/rt2860/common/cmm_aes.c. E.G. the AES code,
>>> please note, this is a staging driver.
>> It's not even the primary driver.  Is there anything that this driver
>> provides that isn't provided by the upstream supported, mainline
>> rt2x00 project?  I.e., can we just delete the staging driver?
>>
>> If we are going to keep the staging driver for some reason, one of the
>> things that should be added to the TODO list would be delete its
>> driver-specific AES code and replace it with calls to the kernel's
>> generic AES code, which among other things, has the advantage that it
>> can take advantage of the AES-NI instructions provided on more modern
>> x86 CPU's.
>>
>>>> I'd like to know who is an appropriate person to discuss this with.
>>> the code is from ralink.
>> David, you might want to contact ralink directly, since it's likely
>> they are distributing that driver with your AES code in other places
>> besides just in the mainstream kernel sources.  Even if we delete the
>> code in the staging tree, they might be distributing that driver still
>> via other means.
>>
> I think it's more fundamental than that.  If ralink -- or anyone else --
> submitted a plagiarized driver to the staging tree, we should remove it
> immediately unless the copyright holder (David in this case) is willing
> to allow us to retain it while things are sorted out.
>
> And yes, David still needs to contact ralink about sorting out the
> violation.
>
> Finally, obviously, a proper Linux driver should use the AES facilities
> in the kernel crypto core.
>
> 	-hpa
Yes I am willing to allow you to retain it.
I guess, to be all legalese..
     I herein permit you to use any 802.11 related C code taken from the 
www.deadhat.com website, in the linux kernel, and to publish it under 
the terms of version 2 of the GNU General Public License.

Yes I've emailed ralink and VIA. I hope they're nice people.

DJ




  parent reply	other threads:[~2011-03-04  5:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 22:49 Why is my copyright code in the linux kernel? dj
2011-03-01 23:30 ` richard -rw- weinberger
2011-03-01 23:54   ` Ted Ts'o
2011-03-02 21:52     ` H. Peter Anvin
2011-03-03  6:04       ` Greg KH
2011-03-04  5:29       ` David Johnston [this message]
2011-03-04  6:34         ` H. Peter Anvin
2011-03-04 22:16           ` Yinghai Lu
2011-03-04 22:19             ` H. Peter Anvin
     [not found]     ` <56a24cfecea63a4752f441056da9c813.squirrel@deadhat.com>
2011-03-03  4:03       ` Greg KH

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=4D7078C8.8050009@deadhat.com \
    --to=dj@deadhat.com \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=tytso@mit.edu \
    /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