From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
David Woodhouse <dwmw2@infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
<ath10k@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 3/3] ath10k: add firmware files
Date: Fri, 14 Mar 2014 19:07:29 +0200 [thread overview]
Message-ID: <87ob18ogj2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAB=NE6WW8yX4kdy02j2fT4g0JvYj4a_XkiqYtXKZSMB7FHuwNg@mail.gmail.com> (Luis R. Rodriguez's message of "Fri, 14 Mar 2014 05:36:53 -0700")
"Luis R. Rodriguez" <mcgrof@do-not-panic.com> writes:
> On Fri, Mar 14, 2014 at 1:45 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>
>> + NO LICENSES OR OTHER RIGHTS,
>> +WHETHER EXPRESS, IMPLIED, BASED ON ESTOPPEL OR OTHERWISE, ARE GRANTED
>> +TO ANY PARTY'S PATENTS, PATENT APPLICATIONS, OR PATENTABLE INVENTIONS
>> +BY VIRTUE OF THIS LICENSE OR THE DELIVERY OR PROVISION BY QUALCOMM
>> +ATHEROS, INC. OF THE SOFTWARE.
>
> This -- however is new to linux-firmware -- and I hereby raise a big
> red fucking flag. All other licenses on linux-firmware provide at the
> very least a limited patent grant. What makes Qualcomm special ?
Well, I was just told to use this license with our firmware, I didn't
write this.
--
Kalle Valo
next prev parent reply other threads:[~2014-03-14 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 8:45 [PATCH 1/3] Rename LICENSE.atheros_firmware to LICENCE.old_qca Kalle Valo
2014-03-14 8:45 ` [PATCH 2/3] ath6k: remove AR6003.1 firmware Kalle Valo
2014-03-16 18:24 ` Ben Hutchings
2014-03-14 8:45 ` [PATCH 3/3] ath10k: add firmware files Kalle Valo
2014-03-14 9:03 ` Kalle Valo
2014-03-16 18:25 ` Ben Hutchings
2014-03-14 12:36 ` Luis R. Rodriguez
2014-03-14 12:47 ` Dave Taht
2014-03-14 15:23 ` Arend van Spriel
2014-03-14 17:07 ` Kalle Valo [this message]
2014-03-14 17:25 ` Luis R. Rodriguez
2014-03-16 18:57 ` Ben Hutchings
2014-03-16 20:17 ` Luis R. Rodriguez
2014-06-25 15:47 ` Luis R. Rodriguez
2014-03-17 8:45 ` Alex Hacker
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=87ob18ogj2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).