From: Kalle Valo <kvalo@codeaurora.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Robert Marko <robimarko@gmail.com>,
ath10k@lists.infradead.org, Skorpy <skorpy@darmstadt.ccc.de>
Subject: Re: Update board-2.bin files in linux-firmware
Date: Sat, 29 Sep 2018 14:19:54 +0300 [thread overview]
Message-ID: <87ftxspn39.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2297652.AArlnWO5DQ@debian64> (Christian Lamparter's message of "Fri, 28 Sep 2018 22:04:54 +0200")
Christian Lamparter <chunkeey@gmail.com> writes:
> On Friday, September 28, 2018 9:28:44 PM CEST Hauke Mehrtens wrote:
>> the ath10k-firmware repository already contains updated board-2.bin
>> files with support for more devices. Please also update the board-2.bin
>> files shipped in the linux-firmware repository as they are normally
>> taken by distributions.
Linux-firmware update is on my todo list, I'm trying to do that next
week but no promises.
> At this opportunity, I would kindly like to remind the maintainer that there
> are currently more pending boardfiles. It would be great if they all could be
> included in the next update as well:
Yeah, these have been on my queue. Thanks for the list, I'll include
them before the update.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-09-29 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 19:28 Update board-2.bin files in linux-firmware Hauke Mehrtens
2018-09-28 20:04 ` Christian Lamparter
2018-09-29 11:19 ` Kalle Valo [this message]
2018-10-08 13:04 ` Kalle Valo
2018-10-09 17:30 ` Christian Lamparter
2018-10-10 11:50 ` 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=87ftxspn39.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=hauke@hauke-m.de \
--cc=robimarko@gmail.com \
--cc=skorpy@darmstadt.ccc.de \
/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