From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: David Johnston <dj@deadhat.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: Fri, 04 Mar 2011 14:19:38 -0800 [thread overview]
Message-ID: <4D71657A.4060604@zytor.com> (raw)
In-Reply-To: <AANLkTim6utrJZ-jVJdNJA6Ea_f8xQ-eAaGX8yfBaT9oc@mail.gmail.com>
On 03/04/2011 02:16 PM, Yinghai Lu wrote:
> On Thu, Mar 3, 2011 at 10:34 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 03/03/2011 09:29 PM, David Johnston wrote:
>>> 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.
>>
>> First of all, thank you (both for the code and for being reasonable.)
>>
>> It sounds like this might simply have been an honest misreading.
>>
>
> interesting.
>
> in the git history, some functions take IN/OUT macro.
>
> -VOID AES_GTK_KEY_UNWRAP(IN UCHAR * key,
> - OUT UCHAR * plaintext,
> - IN UINT32 c_len, IN UCHAR * ciphertext)
>
> so they had driver for other os at first, and ported that one to Linux later ?
>
It's a staging driver for a reason...
-hpa
next prev parent reply other threads:[~2011-03-04 22:19 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
2011-03-04 6:34 ` H. Peter Anvin
2011-03-04 22:16 ` Yinghai Lu
2011-03-04 22:19 ` H. Peter Anvin [this message]
[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=4D71657A.4060604@zytor.com \
--to=hpa@zytor.com \
--cc=dj@deadhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=tytso@mit.edu \
--cc=yinghai@kernel.org \
/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.