From: Sam Leffler <sam@errno.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Bradley M. Kuhn" <bkuhn@softwarefreedom.org>,
Matt Norwood <norwood@softwarefreedom.org>,
Richard Fontana <fontana@softwarefreedom.org>,
karen sandler <karen@softwarefreedom.org>,
Reyk Floeter <reyk@openbsd.org>,
David Kimdon <dwhedon@devicescape.com>
Subject: Re: [PATCH] ath5k - License clarification
Date: Fri, 31 Aug 2007 09:53:06 -0700 [thread overview]
Message-ID: <46D84772.4040308@errno.com> (raw)
In-Reply-To: <43e72e890708310943x55c10044t26e6f8e16292247c@mail.gmail.com>
Luis R. Rodriguez wrote:
> Adding some other copyright holders to the CC list
>
> Luis
>
> On 8/31/07, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>
>> Attached patch amends the ath5k license as per review from SFLC with
>> the following changes:
>>
>> * Makes sure that Reyk's copyright and license notice appears
>> correctly in each file that was derived from his work.
>>
>> * Makes sure that Jiri's changes were released under a permissive,
>> modified-BSD license, as he indicated that was his preference.
>>
>> * Makes sure that Nick's changes were released under
>> GPLv2-or-later, as he indicated that was his preference.
>>
>> * Makes sure that all files clearly have the any GPL notices on
>> top, but include the proper BSD-like notices below when required.
>>
>> * Adds Devicescape attribution to ath5k_base.c
>>
>> * Sets the MODULE_LICENSE to GPL, because with Nick's changes
>> included under only GPL, the module can only be available under GPL.
>>
>> * Adds Nick to the list of MODULE_AUTHORs because his changes
>> are substantial.
>>
>> Signed-Off-By: Bradley M. Kuhn <bkuhn@softwarefreedom.org>
>> Signed-Off-By: Matt Norwood <norwood@softwarefreedom.org>
>> Signed-Off-By: Richard Fontana <fontana@softwarefreedom.org>
>> Signed-Off-By: Karen Sandler <karen@softwarefreedom.org>
>>
>> Acked-by: Luis R. Rodriguez <mcgrof@gmail.com>
>> Acked-by: Jiri Slaby <jirislaby@gmail.com>
>> Acked-by: Nick Kossifidis <mickflemm@gmail.com>
>>
>> Thanks to the SFLC for their help with this driver from legal hell
>>
For the record, I told Jiri and various other folks that any code I
licensed as dual-BSD/GPL could be made GPL only so long as the
attribution remained. That was the exact reason I dual-licensed.
Sam
next prev parent reply other threads:[~2007-08-31 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 16:18 [PATCH] ath5k - License clarification Luis R. Rodriguez
2007-08-31 16:43 ` Luis R. Rodriguez
2007-08-31 16:53 ` Sam Leffler [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-01 19:14 Jacob Meuser
2007-09-01 19:38 ` Jeff Garzik
2007-09-01 20:07 ` Jacob Meuser
2007-09-01 20:32 ` Jeff Garzik
2007-09-01 21:04 ` Jacob Meuser
2007-09-01 21:14 ` Johannes Berg
2007-09-01 21:27 ` Jacob Meuser
2007-09-02 13:42 Mark Kettenis
2007-09-02 14:39 ` Johannes Berg
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=46D84772.4040308@errno.com \
--to=sam@errno.com \
--cc=bkuhn@softwarefreedom.org \
--cc=dwhedon@devicescape.com \
--cc=fontana@softwarefreedom.org \
--cc=jirislaby@gmail.com \
--cc=karen@softwarefreedom.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=norwood@softwarefreedom.org \
--cc=reyk@openbsd.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.