From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath10k@lists.infradead.org
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: Re: Pull request: ath 20141201
Date: Tue, 2 Dec 2014 12:10:59 +0200 [thread overview]
Message-ID: <87ppc2nyz0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20141201205150.GC7266@tuxdriver.com> (John W. Linville's message of "Mon, 1 Dec 2014 15:51:50 -0500")
"John W. Linville" <linville@tuxdriver.com> writes:
> 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.
>>
>> ----------------------------------------------------------------------
[...]
> Pulling now...
Thanks!
ath10k list: I'm planning this to be the last pull request for 3.19. So
anything not commited yet will go to 3.20, for example Device Tree and
WMI TLV stuff. Which is actually a good thing, we get more time for
testing.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-12-02 10:11 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
2014-12-02 10:10 ` 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=87ppc2nyz0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linville@tuxdriver.com \
/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