From: Josh Boyer <jwboyer@kernel.org>
To: Luca Coelho <luca@coelho.fi>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
"linux-wireless@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"kyle@infradead.org" <kyle@infradead.org>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
golan.ben.ami@intel.com
Subject: Re: pull request: iwlwifi firmware updates 2020-10-14
Date: Fri, 23 Oct 2020 08:03:24 -0400 [thread overview]
Message-ID: <CA+5PVA4=R4jJ+jwsj3ayji+PfeV6yVp7T=n1=qF2MUz25iftTQ@mail.gmail.com> (raw)
In-Reply-To: <c26822c0a6d19869d7eeaa6bf07db1f3298a1984.camel@coelho.fi>
Pulled and pushed out.
josh
On Wed, Oct 14, 2020 at 10:01 AM Luca Coelho <luca@coelho.fi> wrote:
>
> Hi,
>
> This contains some new and updated firmwares for all our currently
> maintained FW binaries.
>
> Please pull or let me know if there are any issues.
>
> --
> Cheers,
> Luca.
>
> The following changes since commit 58d41d0facca2478d3e45f6321224361519aee96:
>
> ice: Add comms package file for Intel E800 series driver (2020-10-05 08:09:03 -0400)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git tags/iwlwifi-fw-2020-10-14
>
> for you to fetch changes up to 4f41e9d6437d03e7ce9279076107dd08f46656f3:
>
> iwlwifi: update and add new FWs from core56-54 release (2020-10-14 16:07:28 +0300)
>
> ----------------------------------------------------------------
> Update iwlwifi firmwares to Core56-54
>
> ----------------------------------------------------------------
> Luca Coelho (2):
> iwlwifi: update 3168, 7265D, 8000C and 8265 firmwares
> iwlwifi: update and add new FWs from core56-54 release
>
> WHENCE | 36 ++++++++++++++++++++++++++++++------
> iwlwifi-3168-29.ucode | Bin 1036288 -> 1036288 bytes
> iwlwifi-7265D-29.ucode | Bin 1036656 -> 1036444 bytes
> iwlwifi-8000C-36.ucode | Bin 2401100 -> 2428004 bytes
> iwlwifi-8265-36.ucode | Bin 2409984 -> 2436632 bytes
> iwlwifi-9000-pu-b0-jf-b0-46.ucode | Bin 1481104 -> 1512096 bytes
> iwlwifi-9260-th-b0-jf-b0-46.ucode | Bin 1470272 -> 1483116 bytes
> iwlwifi-Qu-b0-hr-b0-59.ucode | Bin 0 -> 1300764 bytes
> iwlwifi-Qu-b0-jf-b0-59.ucode | Bin 0 -> 1226208 bytes
> iwlwifi-Qu-c0-hr-b0-59.ucode | Bin 0 -> 1300780 bytes
> iwlwifi-Qu-c0-jf-b0-59.ucode | Bin 0 -> 1226224 bytes
> iwlwifi-QuZ-a0-hr-b0-59.ucode | Bin 0 -> 1299660 bytes
> iwlwifi-QuZ-a0-jf-b0-59.ucode | Bin 0 -> 1226064 bytes
> iwlwifi-cc-a0-59.ucode | Bin 0 -> 1261280 bytes
> iwlwifi-ty-a0-gf-a0-59.ucode | Bin 0 -> 1413868 bytes
> 15 files changed, 30 insertions(+), 6 deletions(-)
> create mode 100644 iwlwifi-Qu-b0-hr-b0-59.ucode
> create mode 100644 iwlwifi-Qu-b0-jf-b0-59.ucode
> create mode 100644 iwlwifi-Qu-c0-hr-b0-59.ucode
> create mode 100644 iwlwifi-Qu-c0-jf-b0-59.ucode
> create mode 100644 iwlwifi-QuZ-a0-hr-b0-59.ucode
> create mode 100644 iwlwifi-QuZ-a0-jf-b0-59.ucode
> create mode 100644 iwlwifi-cc-a0-59.ucode
> create mode 100644 iwlwifi-ty-a0-gf-a0-59.ucode
prev parent reply other threads:[~2020-10-23 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 13:22 pull request: iwlwifi firmware updates 2020-10-14 Luca Coelho
2020-10-14 13:22 ` Luca Coelho
2020-10-23 12:03 ` Josh Boyer [this message]
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='CA+5PVA4=R4jJ+jwsj3ayji+PfeV6yVp7T=n1=qF2MUz25iftTQ@mail.gmail.com' \
--to=jwboyer@kernel.org \
--cc=ben@decadent.org.uk \
--cc=golan.ben.ami@intel.com \
--cc=kyle@infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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).