From: Josh Boyer <jwboyer@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linux Firmware <linux-firmware@kernel.org>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: iwlwifi-fw-2021-07-19
Date: Mon, 19 Jul 2021 14:36:32 -0400 [thread overview]
Message-ID: <CA+5PVA7_VythuBOxxUY602YGZZqJD9CLvis6v3ktQMfTFWh+OA@mail.gmail.com> (raw)
In-Reply-To: <20210719112621.21043-1-johannes@sipsolutions.net>
On Mon, Jul 19, 2021 at 7:26 AM Johannes Berg <johannes@sipsolutions.net> wrote:
>
> Hi,
>
> We've got a new Ty device firmware image, along with an
> updated PNVM data file.
>
> Please pull and let me know if there's any problem.
>
> Thanks,
> johannes
>
>
>
> The following changes since commit b7c134f0d3491113958276d631b4e69771a6c5be:
>
> linux-firmware: update NXP 8897/8997 firmware images (2021-07-16 07:55:21 -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-07-19
Pulled and pushed out.
josh
>
> for you to fetch changes up to 5de082d4d0f2db7722c9e6f5c9cff1fefd8073be:
>
> iwlwifi: add ty firmware from Core63-43 (2021-07-19 13:12:20 +0200)
>
> ----------------------------------------------------------------
> iwlwifi: add ty firmware from Core63-43
>
> ----------------------------------------------------------------
> Johannes Berg (1):
> iwlwifi: add ty firmware from Core63-43
>
> LICENCE.iwlwifi_firmware | 2 +-
> WHENCE | 3 +++
> iwlwifi-ty-a0-gf-a0-66.ucode | Bin 0 -> 1477864 bytes
> iwlwifi-ty-a0-gf-a0.pnvm | Bin 27456 -> 27480 bytes
> 4 files changed, 4 insertions(+), 1 deletion(-)
> create mode 100644 iwlwifi-ty-a0-gf-a0-66.ucode
>
prev parent reply other threads:[~2021-07-19 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 11:26 pull-request: iwlwifi-fw-2021-07-19 Johannes Berg
2021-07-19 18:36 ` 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_VythuBOxxUY602YGZZqJD9CLvis6v3ktQMfTFWh+OA@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=johannes@sipsolutions.net \
--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 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).