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-20
Date: Thu, 11 Jan 2018 18:31:06 +0200 [thread overview]
Message-ID: <87efmwtl11.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1513787503.4827.488.camel@coelho.fi> (Luca Coelho's message of "Wed, 20 Dec 2017 18:31:43 +0200")
Luca Coelho <luca@coelho.fi> writes:
> This is my third batch of patches intended for v4.16. 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 f39a5c01c3d24f2f61ec9d8c7d7e81f9aca506ce:
>
> Merge branch 'nfp-flower-add-Geneve-tunnel-support' (2017-12-19 14:52:13 -0500)
>
> 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-20
>
> for you to fetch changes up to 4243edb4704ed950a43440dfb4cbd5613db6ab6c:
>
> iwlwifi: define and use if iwl_mvm_has_tlc_offload (2017-12-20 18:28:25 +0200)
>
> ----------------------------------------------------------------
> Third batch of updates for v4.16
>
> * Small cleanups in the new rate-scaling code;
> * Some improvements in debugging;
> * New FW API changes;
> * Fix a bug where we got a false-positive warning;
> * Fix forced quota debugfs functionality;
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2018-01-11 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 16:31 pull-request: iwlwifi-next 2017-12-20 Luca Coelho
2018-01-11 16:31 ` 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=87efmwtl11.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.