From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 00/13] ath10k: dual-firmware support (MAIN and 10.X)
Date: Fri, 27 Sep 2013 15:30:11 +0300 [thread overview]
Message-ID: <87had6la5o.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1380210437-4391-1-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Thu, 26 Sep 2013 17:47:04 +0200")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> The major changes covered by this work:
> * dynamic WMI structures
> * WMI cmd/event definitions from 10.x FW track
> * memory host chunks feature
> * management frames path over WMI for 10.x
> * WMI RX events handling for MAIN and 10.X split
> * target config split (LARGE AP feature for 10.x)
> * scan start sctructure split
> * dynamic VDEV and PDEV parameters structures
>
> Changes in v2:
> (review comments from Kalle and Michal):
> * WMI cmd, pdev and vdev params names trimmed
> * ath10k_wmi_cmd_init() exposed only
> * few 'if' statements simplifications
> * 10.x mgmt frames over WMI - 'BUG: scheduling while atomic' fixed
>
> Changes in v3:
> * print cmd_id when warning about unsupported WMI command
> * remove excessive empty line
>
> Bartosz Markowski (13):
> ath10k: introduce dynamic WMI structures
> ath10k: add wmi_10x_<cmd/event> definitions
> ath10k: warn if give WMI command is not supported
> ath10k: implement WMI events handling frame for both firmwares
> ath10k: split ath10k_wmi_service_ready_event_rx
> ath10k: drop the fw versioning sanity check
> ath10k: implement host memory chunks
> ath10k: bring back the WMI path for mgmt frames
> ath10k: split wmi_cmd_init path
> ath10k: add TARGET values for 10.x firmware
> ath10k: introduce dynamic vdev parameters
> ath10k: introduce dynamic pdev parameters
> ath10k: handle FW API differences for scan structures
Thanks, all 13 applied.
--
Kalle Valo
prev parent reply other threads:[~2013-09-27 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 15:47 [PATCH v3 00/13] ath10k: dual-firmware support (MAIN and 10.X) Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 01/13] ath10k: introduce dynamic WMI structures Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 02/13] ath10k: add wmi_10x_<cmd/event> definitions Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 03/13] ath10k: warn if give WMI command is not supported Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 04/13] ath10k: implement WMI events handling frame for both firmwares Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 05/13] ath10k: split ath10k_wmi_service_ready_event_rx Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 06/13] ath10k: drop the fw versioning sanity check Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 07/13] ath10k: implement host memory chunks Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 08/13] ath10k: bring back the WMI path for mgmt frames Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 09/13] ath10k: split wmi_cmd_init path Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 10/13] ath10k: add TARGET values for 10.x firmware Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 11/13] ath10k: introduce dynamic vdev parameters Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 12/13] ath10k: introduce dynamic pdev parameters Bartosz Markowski
2013-09-26 15:47 ` [PATCH v3 13/13] ath10k: handle FW API differences for scan structures Bartosz Markowski
2013-09-27 12:30 ` Kalle Valo [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=87had6la5o.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=bartosz.markowski@tieto.com \
--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