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, janet.morgan@intel.com,
joe.konno@intel.com
Subject: Re: pull-request: iwlwifi-next 2017-12-05
Date: Fri, 08 Dec 2017 15:01:25 +0200 [thread overview]
Message-ID: <87tvx1qspm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1512501020.4827.197.camel@coelho.fi> (Luca Coelho's message of "Tue, 05 Dec 2017 21:10:20 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is my second batch of patches intended for v4.16. As I mentioned
> in the patchset thread, I moved patches 5/15 and 6/16 to iwlwifi-fixes.
> Otherwise nothing major here, just the usual continued development.
> 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 80b0ebd488b3edaf3e5ed08c34a952c804e3a635:
>
> Merge tag 'iwlwifi-next-for-kalle-2017-11-29' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next (2017-12-02 15:22:54 +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-2017-12-05
>
> for you to fetch changes up to 0190ff24e55efd3e02479537c2d91835602fffa3:
>
> iwlwifi: mvm: request statistics when reading debugfs (2017-12-05 21:01:43 +0200)
>
> ----------------------------------------------------------------
> Second batch of iwlwifi updates for v4.16
>
> * Initial work for rate-scaling offload;
> * Support for new FW API version;
> * Some fixes here and there;
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2017-12-08 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 19:10 pull-request: iwlwifi-next 2017-12-05 Luca Coelho
2017-12-08 13:01 ` 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=87tvx1qspm.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=david.e.box@intel.com \
--cc=janet.morgan@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