From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Robert Marko <robimarko@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k-firmware: QCA4019 hw1.0/QCA9888 hw2.0: Add OpenMesh A62 specific BDFs
Date: Fri, 20 Apr 2018 09:05:30 +0200 [thread overview]
Message-ID: <2127563.6Z1DauZ1yk@bentobox> (raw)
In-Reply-To: <87zi1zjko7.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2518 bytes --]
On Donnerstag, 19. April 2018 15:11:21 CEST Kalle Valo wrote:
> Thanks for the list, it was really helpful. I think I have now added all
> pending board files, but please let me know if I missed anything.
Sorry about missing the Asus RT-AC58U BDF update.
I went through added files and at least the ones submitted by me look fine
(and I couldn't find anything problematic in the other ones). Thanks for
going through all submissions and integrating them.
pending
=======
* Asus RT-AC58U
- waiting for v2 of the BDFs to be integrated
- http://lists.infradead.org/pipermail/ath10k/2018-January/010770.html
- v1 files: https://github.com/kvalo/ath10k-firmware/commit/a47bcf1e58c4d8914af0951a80fd8861368b700d
accepted
========
* OpenMesh A42
- http://lists.infradead.org/pipermail/ath10k/2017-November/010470.html
- http://lists.infradead.org/pipermail/ath10k/2017-December/010543.html
- https://github.com/kvalo/ath10k-firmware/commit/5cd2bacd8e22217335e539b416d0cb8d59f8e312
* Meraki MR33
- http://lists.infradead.org/pipermail/ath10k/2018-April/011179.html
- https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4
* Compex WLE1216V5-20 + Compex ?
- http://lists.infradead.org/pipermail/ath10k/2018-March/010998.html
- https://github.com/kvalo/ath10k-firmware/commit/b1dd338046a385743c483a47e8eef276adaba0c0
* AVM FRITZ!Box 4040
- http://lists.infradead.org/pipermail/ath10k/2018-April/011178.html
- https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848
* OpenMesh A62
- http://lists.infradead.org/pipermail/ath10k/2018-March/011081.html
- https://github.com/kvalo/ath10k-firmware/commit/a262aac7cfe5ae5833378b4f1b0634f873a4df4d
- https://github.com/kvalo/ath10k-firmware/commit/a315471a5f4c9890e2ed1bdb008b7aae5c885ae0
- https://github.com/kvalo/ath10k-firmware/commit/c3604f7d3ff61d1905aac644c721372f3c2a9663
* GL.iNet GL-B1300
- http://lists.infradead.org/pipermail/ath10k/2018-March/011058.html
- https://github.com/kvalo/ath10k-firmware/commit/c3604f7d3ff61d1905aac644c721372f3c2a9663
* 8devices Jalapeno
- http://lists.infradead.org/pipermail/ath10k/2018-March/010916.html
- https://github.com/kvalo/ath10k-firmware/commit/71e50312b54cc972657a7b08c470088447cb9676
* Netgear EX6100v2/EX6150v2
- http://lists.infradead.org/pipermail/ath10k/2018-February/010845.html
- https://github.com/kvalo/ath10k-firmware/commit/dfe4b7de42e1c40dfd03526ffe7955089c4eef63
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-20 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 10:11 ath10k-firmware: QCA4019 hw1.0/QCA9888 hw2.0: Add OpenMesh A62 specific BDFs Sven Eckelmann
2018-04-19 10:12 ` Kalle Valo
2018-04-19 10:20 ` Kalle Valo
2018-04-19 10:57 ` Sven Eckelmann
2018-04-19 14:21 ` Kalle Valo
2018-04-19 14:33 ` Kalle Valo
2018-04-19 14:47 ` Sven Eckelmann
2018-04-19 15:11 ` Kalle Valo
2018-04-20 7:05 ` Sven Eckelmann [this message]
2018-04-19 16:28 ` Christian Lamparter
2018-04-19 16:51 ` 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=2127563.6Z1DauZ1yk@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=robimarko@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.