From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi@intel.com,
david.e.box@intel.com, joe.konno@intel.com
Subject: Re: pull-request: iwlwifi-next 2019-02-14
Date: Mon, 18 Feb 2019 20:25:44 +0200 [thread overview]
Message-ID: <8736olt0lz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <948cdfe88dcad399e0acb698542fb97a35609059.camel@coelho.fi> (Luca Coelho's message of "Thu, 14 Feb 2019 11:42:45 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is the fourth batch of patches intended for v5.1. This includes
> the last two patchsets I sent. Usual development work. More details
> about the contents in the tag description.
>
> I have sent this out before and kbuildbot reported success.
>
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 34025a1056a3c82b7e16992da9af54d729dd77fe:
>
> rsi: fix indentation issue with a code block (2019-02-08 17:31:23 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git tags/iwlwifi-next-for-kalle-2019-02-14
>
> for you to fetch changes up to 99944b73069d8bcea573c07df8dc8d4f33e78586:
>
> iwlwifi: mvm: stop static queues correctly (2019-02-14 11:29:52 +0200)
>
> ----------------------------------------------------------------
> Fourth batch of iwlwifi patches intended for v5.1
>
> * Work on the new debugging infrastructure continues;
> * FTM (Fine Timing Measurement) initiator and responder implementation;
> * Support for a new device family started;
> * Bump supported FW API to 46;
> * General bugfixes;
> * Other cleanups;
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2019-02-18 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:42 pull-request: iwlwifi-next 2019-02-14 Luca Coelho
2019-02-18 18:25 ` 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=8736olt0lz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=david.e.box@intel.com \
--cc=joe.konno@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
/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