From: Josh Boyer <jwboyer@kernel.org>
To: Luca Coelho <luca@coelho.fi>
Cc: "linux-firmware@kernel.org" <linux-firmware@kernel.org>,
tmb@tmb.nu,
"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 2021-05-12
Date: Wed, 12 May 2021 07:03:42 -0400 [thread overview]
Message-ID: <CA+5PVA52PGAiLpsjpEY1kZive4VrkqvZHCpoyC4Wd6W9CCr=Og@mail.gmail.com> (raw)
In-Reply-To: <c4d8c2f040b368225b72a91e74ee282d9ceab4d5.camel@coelho.fi>
On Wed, May 12, 2021 at 4:33 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 7685cf49917b281b8799ba822e97595eeecb26b5:
>
> nvidia: Update Tegra194 XUSB firmware to v60.09 (2021-05-11 07:48:10 -0400)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git tags/iwlwifi-fw-2021-05-12
>
> for you to fetch changes up to 56115b259807e0417f30ef84bc6d2093572e6901:
>
> iwlwifi: update 8000 family firmwares (2021-05-12 10:53:38 +0300)
>
> ----------------------------------------------------------------
> Update iwllwifi firmwaresto Core60-51
>
> ----------------------------------------------------------------
> Luca Coelho (3):
> iwlwifi: add new FWs from core60-51 release
> iwlwifi: update 9000-family firmwares to core60-51
> iwlwifi: update 8000 family firmwares
>
> WHENCE | 32 ++++++++++++++++++++++++++++----
> iwlwifi-8000C-36.ucode | Bin 2428004 -> 2428004 bytes
> iwlwifi-8265-36.ucode | Bin 2436632 -> 2436632 bytes
> iwlwifi-9000-pu-b0-jf-b0-46.ucode | Bin 1514240 -> 1514876 bytes
> iwlwifi-9260-th-b0-jf-b0-46.ucode | Bin 1485556 -> 1485620 bytes
> iwlwifi-Qu-b0-hr-b0-63.ucode | Bin 0 -> 1334856 bytes
> iwlwifi-Qu-b0-jf-b0-63.ucode | Bin 0 -> 1252748 bytes
> iwlwifi-Qu-c0-hr-b0-63.ucode | Bin 0 -> 1334872 bytes
> iwlwifi-Qu-c0-jf-b0-63.ucode | Bin 0 -> 1252764 bytes
> iwlwifi-QuZ-a0-hr-b0-63.ucode | Bin 0 -> 1334804 bytes
> iwlwifi-QuZ-a0-jf-b0-63.ucode | Bin 0 -> 1252744 bytes
> iwlwifi-cc-a0-63.ucode | Bin 0 -> 1298688 bytes
> iwlwifi-ty-a0-gf-a0-63.ucode | Bin 0 -> 1460012 bytes
> iwlwifi-ty-a0-gf-a0.pnvm | Bin 27456 -> 27456 bytes
> 14 files changed, 28 insertions(+), 4 deletions(-)
> create mode 100644 iwlwifi-Qu-b0-hr-b0-63.ucode
> create mode 100644 iwlwifi-Qu-b0-jf-b0-63.ucode
> create mode 100644 iwlwifi-Qu-c0-hr-b0-63.ucode
> create mode 100644 iwlwifi-Qu-c0-jf-b0-63.ucode
> create mode 100644 iwlwifi-QuZ-a0-hr-b0-63.ucode
> create mode 100644 iwlwifi-QuZ-a0-jf-b0-63.ucode
> create mode 100644 iwlwifi-cc-a0-63.ucode
> create mode 100644 iwlwifi-ty-a0-gf-a0-63.ucode
Pulled and pushed out. Thanks.
josh
prev parent reply other threads:[~2021-05-12 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 8:00 pull request: iwlwifi firmware updates 2021-05-12 Luca Coelho
2021-05-12 8:00 ` Luca Coelho
2021-05-12 11: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+5PVA52PGAiLpsjpEY1kZive4VrkqvZHCpoyC4Wd6W9CCr=Og@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 \
--cc=tmb@tmb.nu \
/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).