From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "Hutchings, Ben" <ben@decadent.org.uk>,
"kyle@infradead.org" <kyle@infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Ben Ami, Golan" <golan.ben.ami@intel.com>,
"jwboyer@kernel.org" <jwboyer@kernel.org>,
"Yang, You-Sheng" <vicamo.yang@canonical.com>
Subject: pull request: iwlwifi firmware updates 2022-11-08
Date: Tue, 8 Nov 2022 17:35:25 +0000 [thread overview]
Message-ID: <79b625f47ae9ed8fd9784471dff0deb5ecb2c2f1.camel@intel.com> (raw)
Hi,
This contains some new firmwares for all our currently maintained FW binaries.
Please pull or let me know if there are any issues.
--
Thanks
Gregory
The following changes since commit 8bb75626e9dd831d323c4e460414b56260f0b700:
Merge branch 'for-upstream' of https://github.com/CirrusLogic/linux-firmware (2022-10-31 11:12:54 -0400)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git tags/iwlwifi-fw-2022-11-08
for you to fetch changes up to 4a733c26d7a2ea93c06bfb793d6c878bc19a2c3c:
iwlwifi: add new FWs from core74_pv-60 release (2022-11-08 18:05:52 +0200)
----------------------------------------------------------------
add new FWs from core74_pv-60 release
----------------------------------------------------------------
Gregory Greenman (1):
iwlwifi: add new FWs from core74_pv-60 release
WHENCE | 36 ++++++++++++++++++++++++++++++++++++
iwlwifi-Qu-b0-hr-b0-77.ucode | Bin 0 -> 1407736 bytes
iwlwifi-Qu-b0-jf-b0-77.ucode | Bin 0 -> 1325500 bytes
iwlwifi-Qu-c0-hr-b0-77.ucode | Bin 0 -> 1407752 bytes
iwlwifi-Qu-c0-jf-b0-77.ucode | Bin 0 -> 1325516 bytes
iwlwifi-QuZ-a0-hr-b0-77.ucode | Bin 0 -> 1406756 bytes
iwlwifi-QuZ-a0-jf-b0-77.ucode | Bin 0 -> 1325532 bytes
iwlwifi-cc-a0-77.ucode | Bin 0 -> 1369192 bytes
iwlwifi-so-a0-gf-a0-77.ucode | Bin 0 -> 1641260 bytes
iwlwifi-so-a0-gf-a0.pnvm | Bin 42092 -> 42092 bytes
iwlwifi-so-a0-gf4-a0-77.ucode | Bin 0 -> 1669164 bytes
iwlwifi-so-a0-gf4-a0.pnvm | Bin 28064 -> 28252 bytes
iwlwifi-so-a0-hr-b0-77.ucode | Bin 0 -> 1500532 bytes
iwlwifi-so-a0-jf-b0-77.ucode | Bin 0 -> 1446036 bytes
iwlwifi-ty-a0-gf-a0-77.ucode | Bin 0 -> 1594276 bytes
iwlwifi-ty-a0-gf-a0.pnvm | Bin 41876 -> 41876 bytes
16 files changed, 36 insertions(+)
create mode 100644 iwlwifi-Qu-b0-hr-b0-77.ucode
create mode 100644 iwlwifi-Qu-b0-jf-b0-77.ucode
create mode 100644 iwlwifi-Qu-c0-hr-b0-77.ucode
create mode 100644 iwlwifi-Qu-c0-jf-b0-77.ucode
create mode 100644 iwlwifi-QuZ-a0-hr-b0-77.ucode
create mode 100644 iwlwifi-QuZ-a0-jf-b0-77.ucode
create mode 100644 iwlwifi-cc-a0-77.ucode
create mode 100644 iwlwifi-so-a0-gf-a0-77.ucode
create mode 100644 iwlwifi-so-a0-gf4-a0-77.ucode
create mode 100644 iwlwifi-so-a0-hr-b0-77.ucode
create mode 100644 iwlwifi-so-a0-jf-b0-77.ucode
create mode 100644 iwlwifi-ty-a0-gf-a0-77.ucode
next reply other threads:[~2022-11-08 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 17:35 Greenman, Gregory [this message]
2022-11-09 17:50 ` pull request: iwlwifi firmware updates 2022-11-08 Josh Boyer
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=79b625f47ae9ed8fd9784471dff0deb5ecb2c2f1.camel@intel.com \
--to=gregory.greenman@intel.com \
--cc=ben@decadent.org.uk \
--cc=golan.ben.ami@intel.com \
--cc=jwboyer@kernel.org \
--cc=kyle@infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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.