From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: "linux-firmware\@kernel.org" <linux-firmware@kernel.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>,
"ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>,
"ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PULL linux-firmware] ath10k & ath11k firmware 20220423
Date: Fri, 29 Apr 2022 08:44:24 +0300 [thread overview]
Message-ID: <87k0b8fnpj.fsf@kernel.org> (raw)
In-Reply-To: <332e62e5-b04d-3a6a-38fe-924d056bf0f8@linaro.org> (Dmitry Baryshkov's message of "Fri, 29 Apr 2022 02:43:38 +0300")
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
> Hi Kalle,
>
> On 27/04/2022 11:32, Kalle Valo wrote:
>> Add support for QCN9074 and WCN6750 ath11k hardware families. Also
>> there are several updates to existing firmwares and board files for both ath10k
>> and ath11k.
>>
>> Please let me know if there are any problems.
>
> I noticed that this pull request doesn't include the board file for
> WCN3990. Is there any issue with it that we can solve on our side?
Oh, sorry about that. I guess this is just a bug in my scripts, I'll
include the wcn3990 board file in the next pull request.
Linux firmware maintainers, please pull this anyway. I'll submit a
follow up pull request later.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2022-04-29 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 8:32 [PULL linux-firmware] ath10k & ath11k firmware 20220423 Kalle Valo
2022-04-28 23:43 ` Dmitry Baryshkov
2022-04-29 5:44 ` Kalle Valo [this message]
2022-04-29 6:12 ` Dmitry Baryshkov
2022-06-01 6:44 ` Kalle Valo
2022-06-01 10:34 ` Dmitry Baryshkov
2022-05-02 12:32 ` 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=87k0b8fnpj.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=dmitry.baryshkov@linaro.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