From: Stefan Wahren <stefan.wahren@i2se.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Josh Boyer <jwboyer@kernel.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
linux-firmware@kernel.org
Subject: Re: Fwd: [PATCH V3 1/5] brcm: update firmware for bcm43430
Date: Fri, 25 May 2018 11:21:25 +0200 [thread overview]
Message-ID: <6d010b79-e335-7c8d-dc14-198d345b9607@i2se.com> (raw)
In-Reply-To: <5AF95EF8.3020504@broadcom.com>
Hi Arend,
[add Josh]
Am 14.05.2018 um 12:03 schrieb Arend van Spriel:
> Hi Stefan,
>
> Your query kept nagging as I recalled firmware patches earlier *this*
> year, not november last year. Searched my mailing list archive and
> found this. Apparently, it got lost in the cracks. Let's ping the
> firmware maintainers...
could you please resend instead forward?
Thanks
Stefan
>
> Regards,
> Arend
next prev parent reply other threads:[~2018-05-25 9:21 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 [this message]
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
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=6d010b79-e335-7c8d-dc14-198d345b9607@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--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.