From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Linux Firmware <linux-firmware@kernel.org>,
chi-hsien.lin@cypress.com,
Linux Wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, wright.feng@cypress.com,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH V3 0/5] Update brcm firmware files
Date: Tue, 15 May 2018 10:43:28 +0200 [thread overview]
Message-ID: <5AFA9DB0.7060703@broadcom.com> (raw)
In-Reply-To: <CA+5PVA7m3wWHyi12rTcpAozj=en9BtnsVAKAbQyvKvPRh_jC4A@mail.gmail.com>
On 5/14/2018 2:05 PM, Josh Boyer wrote:
> n Mon, May 14, 2018 at 6:11 AM Arend van Spriel <
> arend.vanspriel@broadcom.com> wrote:
>
>> On 3/16/2018 3:08 PM, Chi-Hsien Lin wrote:
>>> Update brcm firmware files and WHENCE accordingly.
>
>> Hi firmware-maintainers,
>
>> It seems this series somehow got lost. Can these still be applied. They
>> can be found in the linux-wireless patchwork database. I provided links
>> below.
>
> All 5 of these move the respective firmware files under the Cypress
> license. It has been pointed out that the Cypress license has some
> questionable language in it and that people have been in touch to try and
> get this resolved. I'm personally waiting on applying them until the
> licence issue is sorted out.
Thanks, Josh
I could not find any such response. Has it been taken off-list? Seems
like 2 months is quite some time, but maybe there are lawyers involved ;-)
Regards,
Arend
next prev parent reply other threads:[~2018-05-15 8:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:08 [PATCH V3 0/5] Update brcm firmware files Chi-Hsien Lin
2018-03-16 14:08 ` [PATCH V3 1/5] brcm: update firmware for bcm43430 Chi-Hsien Lin
2018-05-14 10:03 ` Fwd: " Arend van Spriel
2018-05-25 9:21 ` Stefan Wahren
2018-03-16 14:08 ` [PATCH V3 2/5] brcm: update firmware for bcm43340 Chi-Hsien Lin
2018-03-16 14:08 ` [PATCH V3 3/5] brcm: update firmware for bcm43362 Chi-Hsien Lin
2018-03-16 14:08 ` [PATCH V3 4/5] brcm: update firmware for bcm4354 Chi-Hsien Lin
2018-03-16 14:08 ` [PATCH V3 5/5] brcm: update firmware for bcm4356 pcie Chi-Hsien Lin
2018-05-14 10:11 ` [PATCH V3 0/5] Update brcm firmware files Arend van Spriel
2018-05-14 12:05 ` Josh Boyer
2018-05-15 8:43 ` Arend van Spriel [this message]
2018-05-18 7:04 ` Hans de Goede
2018-05-18 9:00 ` Arend van Spriel
2018-05-18 9:45 ` Hans de Goede
2018-05-21 10:44 ` Chi-Hsien Lin
2018-05-27 14:37 ` Hans de Goede
2018-05-30 7:28 ` Chi-Hsien Lin
2018-05-30 7:48 ` Hans de Goede
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=5AFA9DB0.7060703@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.com \
/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.