From: Kalle Valo <kvalo@codeaurora.org>
To: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>,
"ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PULL] ath10k & ath11k firmware 20201022
Date: Thu, 22 Oct 2020 21:26:30 +0300 [thread overview]
Message-ID: <87sga65d7t.fsf@codeaurora.org> (raw)
In-Reply-To: <BYAPR02MB4567892AD5957F360C01E73F921D0@BYAPR02MB4567.namprd02.prod.outlook.com> (Kalle Valo's message of "Thu, 22 Oct 2020 08:23:01 +0000")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Hi linux-firmware maintainers,
>
> here's a pull request for ath10k and ath11k drivers. For ath10k there
> is a firmware for new hardware QCA6174 hw3.0 SDIO. For ath11k there
> are firmwares for new hardware IPQ8074 hw2.0, IPQ6018 hw1.0 and
> QCA6390 hw2.0. And also few updates for existing hardware.
>
> I did not include QCA9377 SDIO firmware as I saw Christian submitted a
> patch adding that.
>
> Please let me know if there are any problems.
>
> Kalle
>
> The following changes since commit 58d41d0facca2478d3e45f6321224361519aee96:
>
> ice: Add comms package file for Intel E800 series driver (2020-10-05 08:09:03 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/linux-firmware.git ath10k-20201022
I noticed that ath11k Notice.txt files are not valid utf-8. Please drop
this pull request, I'll send a fixed one tomorrow.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-10-22 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 8:23 [PULL] ath10k & ath11k firmware 20201022 Kalle Valo
2020-10-22 18:26 ` Kalle Valo [this message]
2020-10-22 18:26 ` Kalle Valo
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=87sga65d7t.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--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).