From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
ath6kl-devel@qca.qualcomm.com
Subject: Re: Pull request: ath 20131017
Date: Fri, 18 Oct 2013 13:57:33 -0400 [thread overview]
Message-ID: <20131018175732.GD28130@tuxdriver.com> (raw)
In-Reply-To: <87mwm82rmu.fsf@kamboji.qca.qualcomm.com>
On Thu, Oct 17, 2013 at 12:06:33PM +0300, Kalle Valo wrote:
> Hi John,
>
> here's a pull request for ath6kl and ath10k. Notable changes:
>
> Bartosz added support to ath10k for our 10.x AP firmware branch, which
> gives us AP specific features and fixes. We still support the main
> firmware branch as well just like before, ath10k detects runtime what
> firmware is used. Unfortunately the firmware interface in 10.x branch is
> somewhat different so there was quite a lot of changes in ath10k for
> this.
>
> Michal and Sujith did some performance improvements in ath10k. Vladimir
> fixed a compiler warning and Fengguang removed an extra semicolon.
>
> Please let me know if there are any problems.
>
> Kalle
>
> The following changes since commit 6e712d427cb0542afdd5220edb6e4f4f8a5b952d:
>
> ath10k: replenish HTT RX buffers in a tasklet (2013-09-26 17:22:54 +0300)
>
> are available in the git repository at:
>
> git://github.com/kvalo/ath.git for-linville
>
> for you to fetch changes up to 56b84287d14aa74823a9c290d0c5839d38365110:
>
> ath10k: add might_sleep() to ath10k_wmi_cmd_send() (2013-10-16 15:44:47 +0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-10-18 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:06 Pull request: ath 20131017 Kalle Valo
2013-10-18 17:57 ` John W. Linville [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=20131018175732.GD28130@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath10k@lists.infradead.org \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=kvalo@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).