All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Josh Boyer <jwboyer@kernel.org>
Cc: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Thu, 10 Feb 2022 12:45:32 +0200	[thread overview]
Message-ID: <87ee4brodv.fsf@kernel.org> (raw)
In-Reply-To: <CA+5PVA4WEuJDB3OCKfYK-BPaccpVWd9t_au9S7MCEtpy7cdF-A@mail.gmail.com> (Josh Boyer's message of "Wed, 29 Dec 2021 08:41:45 -0500")

Hi Josh,

Josh Boyer <jwboyer@kernel.org> writes:

> On Thu, Dec 23, 2021 at 9:03 AM Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>
>>  WHENCE                           |   14 +-
>>  ath11k/IPQ6018/hw1.0/Notice.txt  |   48 +-
>
> These Notice files seem problematic.  They're clearly well intended,
> but they have language that alludes to an agreement with Atheros and a
> confidential nature to some of the files.  Specifically:
>
> "...your use of these software
> components together with the Qualcomm Atheros software (Qualcomm
> Atheros software hereinafter referred to as “Software”) is
> subject to the terms of your agreement from Qualcomm Atheros."
>
> Nobody has an opportunity to agree to anything with Atheros when they
> consume the files from linux-firmware.  There's also no explicit grant
> of redistribution for any of these files.

So this file we are discussing is the notice.txt file. In the WHENCE
file the actual license for ath11k is:

Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details

Does that cover your concerns about redistribution?

I'm still working on your other comment about notice.txt, will get back
on that later.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Josh Boyer <jwboyer@kernel.org>
Cc: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>,
	 "linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	 "ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Thu, 10 Feb 2022 12:45:32 +0200	[thread overview]
Message-ID: <87ee4brodv.fsf@kernel.org> (raw)
In-Reply-To: <CA+5PVA4WEuJDB3OCKfYK-BPaccpVWd9t_au9S7MCEtpy7cdF-A@mail.gmail.com> (Josh Boyer's message of "Wed, 29 Dec 2021 08:41:45 -0500")

Hi Josh,

Josh Boyer <jwboyer@kernel.org> writes:

> On Thu, Dec 23, 2021 at 9:03 AM Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>
>>  WHENCE                           |   14 +-
>>  ath11k/IPQ6018/hw1.0/Notice.txt  |   48 +-
>
> These Notice files seem problematic.  They're clearly well intended,
> but they have language that alludes to an agreement with Atheros and a
> confidential nature to some of the files.  Specifically:
>
> "...your use of these software
> components together with the Qualcomm Atheros software (Qualcomm
> Atheros software hereinafter referred to as “Software”) is
> subject to the terms of your agreement from Qualcomm Atheros."
>
> Nobody has an opportunity to agree to anything with Atheros when they
> consume the files from linux-firmware.  There's also no explicit grant
> of redistribution for any of these files.

So this file we are discussing is the notice.txt file. In the WHENCE
file the actual license for ath11k is:

Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details

Does that cover your concerns about redistribution?

I'm still working on your other comment about notice.txt, will get back
on that later.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2022-02-10 10:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 14:03 [PULL] ath11k firmware 20211223 Kalle Valo
2021-12-23 14:03 ` Kalle Valo
2021-12-23 17:24 ` Mark Herbert
2021-12-29 13:41 ` Josh Boyer
2021-12-29 13:41   ` Josh Boyer
2022-01-10 15:19   ` Kalle Valo
2022-01-10 15:19     ` Kalle Valo
2022-02-10 10:45   ` Kalle Valo [this message]
2022-02-10 10:45     ` Kalle Valo
2022-02-18 15:55     ` Josh Boyer
2022-02-18 15:55       ` Josh Boyer
2022-03-02 17:50       ` Jouni Malinen
2022-03-02 17:50         ` Jouni Malinen
2022-03-04 13:04         ` Josh Boyer
2022-03-04 13:04           ` Josh Boyer
2022-03-04 16:14           ` Jouni Malinen
2022-03-04 16:14             ` Jouni Malinen
2022-03-23  8:06             ` Takashi Iwai
2022-03-23  8:06               ` Takashi Iwai
2022-04-13  8:26               ` Kalle Valo
2022-04-13  8:26                 ` Kalle Valo
2022-04-13  8:40                 ` Takashi Iwai
2022-04-13  8:40                   ` Takashi Iwai
2022-02-18 15:00 ` Sven Eckelmann
2022-02-18 15:00   ` Sven Eckelmann
2022-04-13  8:28   ` Kalle Valo
2022-04-13  8:28     ` Kalle Valo

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=87ee4brodv.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@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 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.