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 20141201
Date: Mon, 1 Dec 2014 15:51:50 -0500 [thread overview]
Message-ID: <20141201205150.GC7266@tuxdriver.com> (raw)
In-Reply-To: <871tojr16m.fsf@kamboji.qca.qualcomm.com>
On Mon, Dec 01, 2014 at 02:42:41PM +0200, Kalle Valo wrote:
> Hi John,
>
> here's a pull request I'm hoping still to get to 3.19. The changelog is
> below. Please let me know if you have any problems.
>
> ----------------------------------------------------------------------
> Only ath10k changes this time and no major changes. Most visible are:
>
> o new debugfs interface for runtime firmware debugging (Yanbo)
>
> o fix shared WEP (Sujith)
>
> o don't rebuild whenever kernel version changes (Johannes)
>
> o lots of refactoring to make it easier to add new hw support (Michal)
>
> There's also smaller fixes and improvements with no point of listing
> here.
>
> ----------------------------------------------------------------------
>
>
> The following changes since commit 47b6308b643302e642ca2a5cb6470926f7e1c428:
>
> ath9k: Move roc completion to the offchannel timer (2014-11-17 15:32:17 -0500)
>
> are available in the git repository at:
>
> git://github.com/kvalo/ath.git for-linville
>
> for you to fetch changes up to fe2407a889f7b6530b7e231e7c866f5c5d223657:
>
> ath10k: simplify rx ring size/fill calculation (2014-12-01 09:29:27 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-12-01 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 12:42 Pull request: ath 20141201 Kalle Valo
2014-12-01 20:51 ` John W. Linville [this message]
2014-12-02 10:10 ` 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=20141201205150.GC7266@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