From: Josh Boyer <jwboyer@kernel.org>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Linux Firmware <linux-firmware@kernel.org>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Brian Norris <briannorris@chromium.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH v3 0/3] rtw88: update 8822c firmware files
Date: Thu, 15 Aug 2019 07:42:14 -0400 [thread overview]
Message-ID: <CA+5PVA4rM1u4C-c-_efonrYgX6vFaCAt0kfJnAq7Tc33HRWRUA@mail.gmail.com> (raw)
In-Reply-To: <1565252549-25524-1-git-send-email-yhchuang@realtek.com>
On Thu, Aug 8, 2019 at 4:22 AM <yhchuang@realtek.com> wrote:
>
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> Update 8822c firmware image, and add wowlan firmware.
> Also add a README to describe its usage.
>
> Yan-Hsuan Chuang (3):
> rtw88: RTL8822C: update rtw8822c_fw.bin to v7.3
> rtw88: RTL8822C: add WoW firmware v7.3
> rtw88: add a README file
>
> WHENCE | 1 +
> rtw88/README | 28 ++++++++++++++++++++++++++++
> rtw88/rtw8822c_fw.bin | Bin 184640 -> 189152 bytes
> rtw88/rtw8822c_wow_fw.bin | Bin 0 -> 138720 bytes
> 4 files changed, 29 insertions(+)
> create mode 100644 rtw88/README
> create mode 100755 rtw88/rtw8822c_wow_fw.bin
All three applied and pushed out. I edited the third patch to add the
README to WHENCE.
josh
prev parent reply other threads:[~2019-08-15 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 8:22 [PATCH v3 0/3] rtw88: update 8822c firmware files yhchuang
2019-08-08 8:22 ` [PATCH v3 1/3] rtw88: RTL8822C: update rtw8822c_fw.bin to v7.3 yhchuang
2019-08-08 8:22 ` [PATCH v3 2/3] rtw88: RTL8822C: add WoW firmware v7.3 yhchuang
2019-08-08 8:22 ` [PATCH v3 3/3] rtw88: add a README file yhchuang
2019-08-15 11:42 ` 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+5PVA4rM1u4C-c-_efonrYgX6vFaCAt0kfJnAq7Tc33HRWRUA@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arend.vanspriel@broadcom.com \
--cc=briannorris@chromium.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yhchuang@realtek.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 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).