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,
	ath6kl@lists.infradead.org
Subject: Re: Pull request: ath 20140717
Date: Fri, 18 Jul 2014 13:45:15 -0400	[thread overview]
Message-ID: <20140718174515.GF31114@tuxdriver.com> (raw)
In-Reply-To: <87k37c6kw6.fsf@kamboji.qca.qualcomm.com>

On Thu, Jul 17, 2014 at 06:54:33PM +0300, Kalle Valo wrote:
> Hi John,
> 
> here's new pull request for 3.17. Major changes are:
> 
> For ath6kl me and Jessica added support for ar6004 hw3.0, our latest
> version of ar6004.
> 
> For ath10k Janusz added a printout so that it's easier to check what
> ath10k kconfig options are enabled. He also added a debugfs file to
> configure maximum amsdu and ampdu values. Also we had few fixes as
> usual.
> 
> Please let me know if there are any problems.
> 
> Kalle
> 
> The following changes since commit a715c7ddd65a1a3b2839b8ebd759bb2d361f7675:
> 
>   wil6210: improve debug for WMI receive (2014-05-30 13:49:34 -0400)
> 
> are available in the git repository at:
> 
>   git://github.com/kvalo/ath.git tags/for-linville-20140717
> 
> for you to fetch changes up to 993619443774f7ef4df3b98655df4c3bf298548c:
> 
>   ath10k: sanitize tx ring index access properly (2014-07-15 11:19:45 +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.

      reply	other threads:[~2014-07-18 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 15:54 Pull request: ath 20140717 Kalle Valo
2014-07-18 17:45 ` 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=20140718174515.GF31114@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath10k@lists.infradead.org \
    --cc=ath6kl@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).