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,
You-Sheng Yang <vicamo.yang@canonical.com>
Subject: Re: pull request: iwlwifi firmware updates 2022-01-10 v2
Date: Mon, 10 Jan 2022 13:21:07 -0500 [thread overview]
Message-ID: <CA+5PVA7+uGhN+c2QBj41ieCPW1n6R8yd16ki9sB+Dx6ZVqUs9w@mail.gmail.com> (raw)
In-Reply-To: <2aa6a2bb7efda2b9b322371211eff7a7d0aae706.camel@coelho.fi>
On Mon, Jan 10, 2022 at 12:36 PM Luca Coelho <luca@coelho.fi> wrote:
>
> Hi,
>
> This contains some new and updated firmwares for all our currently
> maintained FW binaries.
>
> In v2, I fixed the so/s0 issue in WHENCE.
>
> Please pull or let me know if there are any issues.
>
> --
> Cheers,
> Luca.
>
>
> The following changes since commit 182a186c570baab3968ca9116ee58b1875fb0168:
>
> Merge branch 'for-upstream' of git://git.chelsio.net/pub/git/linux-firmware into main (2022-01-07 07:20:18 -0500)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git tags/iwlwifi-fw-2022-01-10-v2
>
> for you to fetch changes up to 23e0197e9e6fe9ca0d2ead3a3df3c41df97ad16b:
>
> iwlwifi: add new FWs from core66-88 release (2022-01-10 19:30:31 +0200)
>
> ----------------------------------------------------------------
> Update and add iwlwifi firmware binaries for release Core66-88
>
> ----------------------------------------------------------------
> Luca Coelho (2):
> iwlwifi: update 9000-family firmwares to core66-88
> iwlwifi: add new FWs from core66-88 release
Thanks. Pulled and pushed out.
josh
>
> WHENCE | 44 ++++++++++++++++++++++++++++++++++++++++++--
> iwlwifi-9000-pu-b0-jf-b0-46.ucode | Bin 1519264 -> 1519544 bytes
> iwlwifi-9260-th-b0-jf-b0-46.ucode | Bin 1490096 -> 1490376 bytes
> iwlwifi-Qu-b0-hr-b0-68.ucode | Bin 0 -> 1355836 bytes
> iwlwifi-Qu-b0-jf-b0-68.ucode | Bin 0 -> 1275268 bytes
> iwlwifi-Qu-c0-hr-b0-68.ucode | Bin 0 -> 1355852 bytes
> iwlwifi-Qu-c0-jf-b0-68.ucode | Bin 0 -> 1275284 bytes
> iwlwifi-QuZ-a0-hr-b0-68.ucode | Bin 0 -> 1355800 bytes
> iwlwifi-QuZ-a0-jf-b0-68.ucode | Bin 0 -> 1275264 bytes
> iwlwifi-cc-a0-68.ucode | Bin 0 -> 1314392 bytes
> iwlwifi-so-a0-gf-a0-68.ucode | Bin 0 -> 1533812 bytes
> iwlwifi-so-a0-gf-a0.pnvm | Bin 41804 -> 41808 bytes
> iwlwifi-so-a0-gf4-a0-68.ucode | Bin 0 -> 1552216 bytes
> iwlwifi-so-a0-gf4-a0.pnvm | Bin 21576 -> 21576 bytes
> iwlwifi-so-a0-hr-b0-68.ucode | Bin 0 -> 1429192 bytes
> iwlwifi-so-a0-jf-b0-68.ucode | Bin 0 -> 1378284 bytes
> iwlwifi-ty-a0-gf-a0-68.ucode | Bin 0 -> 1494304 bytes
> iwlwifi-ty-a0-gf-a0.pnvm | Bin 41612 -> 41588 bytes
> 18 files changed, 42 insertions(+), 2 deletions(-)
> create mode 100644 iwlwifi-Qu-b0-hr-b0-68.ucode
> create mode 100644 iwlwifi-Qu-b0-jf-b0-68.ucode
> create mode 100644 iwlwifi-Qu-c0-hr-b0-68.ucode
> create mode 100644 iwlwifi-Qu-c0-jf-b0-68.ucode
> create mode 100644 iwlwifi-QuZ-a0-hr-b0-68.ucode
> create mode 100644 iwlwifi-QuZ-a0-jf-b0-68.ucode
> create mode 100644 iwlwifi-cc-a0-68.ucode
> create mode 100644 iwlwifi-so-a0-gf-a0-68.ucode
> create mode 100644 iwlwifi-so-a0-gf4-a0-68.ucode
> create mode 100644 iwlwifi-so-a0-hr-b0-68.ucode
> create mode 100644 iwlwifi-so-a0-jf-b0-68.ucode
> create mode 100644 iwlwifi-ty-a0-gf-a0-68.ucode
>
prev parent reply other threads:[~2022-01-10 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 17:36 pull request: iwlwifi firmware updates 2022-01-10 v2 Luca Coelho
2022-01-10 18:21 ` 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+5PVA7+uGhN+c2QBj41ieCPW1n6R8yd16ki9sB+Dx6ZVqUs9w@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=vicamo.yang@canonical.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.