linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: Pull request: ath 20140514
Date: Wed, 14 May 2014 15:40:29 -0400	[thread overview]
Message-ID: <20140514194029.GE14183@tuxdriver.com> (raw)
In-Reply-To: <87zjikfqus.fsf@kamboji.qca.qualcomm.com>

Were you hoping for 3.15 for these?

On Wed, May 14, 2014 at 04:10:35PM +0300, Kalle Valo wrote:
> Hi John,
> 
> small pull request this time. I'll promise next one will be bigger ;)
> 
> Changelog for the request:
> 
> For ath10k Michal did various small fixes on how we handle
> hardware/firmware problems and he also fixed two memory leaks.
> 
> Please let me know if there are any problems.
> 
> The following changes since commit 644aa4d62096039a79987e13062c6fc656ea380c:
> 
>   b43: remove list of IEEE 802.11 devices (2014-04-22 15:06:34 -0400)
> 
> are available in the git repository at:
> 
>   git://github.com/kvalo/ath.git for-linville
> 
> for you to fetch changes up to d9bc4b9b693d52dc14dc1de5dfec760634067d8c:
> 
>   ath10k: fix firmware recovery with ap interface (2014-04-24 09:23:03 +0300)
> 
> ----------------------------------------------------------------
> Michal Kazior (7):
>       ath10k: differentiate between target init failures
>       ath10k: don't wait for device init if it crashed
>       ath10k: skip suspending when recovering
>       ath10k: make sure to not leak beacon dma mapping
>       ath10k: make sure to not use invalid beacon pointer
>       ath10k: prevent beacon memory leak
>       ath10k: fix firmware recovery with ap interface
> 
>  drivers/net/wireless/ath/ath10k/core.c |    6 ++++--
>  drivers/net/wireless/ath/ath10k/mac.c  |   16 ++++++++++++++++
>  drivers/net/wireless/ath/ath10k/pci.c  |   18 +++++++++++++++++-
>  drivers/net/wireless/ath/ath10k/wmi.c  |    2 ++
>  4 files changed, 39 insertions(+), 3 deletions(-)
> 
> -- 
> Kalle Valo
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2014-05-14 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 13:10 Pull request: ath 20140514 Kalle Valo
2014-05-14 19:40 ` John W. Linville [this message]
2014-05-14 19:52   ` Kalle Valo
2014-05-16 18:15 ` John W. Linville

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=20140514194029.GE14183@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath10k@lists.infradead.org \
    --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).