From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org, linuxwifi <linuxwifi@intel.com>
Subject: Re: pull-request: iwlwifi 2017-12-05
Date: Thu, 07 Dec 2017 15:52:01 +0200 [thread overview]
Message-ID: <877etyve66.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1512484624.4827.187.camel@coelho.fi> (Luca Coelho's message of "Tue, 05 Dec 2017 16:37:04 +0200")
Luca Coelho <luca@coelho.fi> writes:
> Here is my third set of fixes for 4.15. The most important fixes are
> for the new 9000 series where we were not handling some offloads
> correctly and secure connections were totally broken. There is also 4
> new PCI IDs and an ROC fix on P2P. More details in the tag
> description.
>
> I have sent this out before and kbuildbot didn't find any issues.
> Please let me know if there are any issues.
>
> Cheers,
> Luca.
>
>
> The following changes since commit 5c3de777bdaf48bd0cfb43097c0d0fb85056cab7:
>
> brcmfmac: change driver unbind order of the sdio function devices (2017-12-02 17:22:47 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git tags/iwlwifi-for-kalle-2017-12-05
>
> for you to fetch changes up to bf19037074e770aad74b3b90f37b8b98db3f3748:
>
> iwlwifi: mvm: mark MIC stripped MPDUs (2017-12-05 16:23:30 +0200)
>
> ----------------------------------------------------------------
> Third batch of iwlwifi patches intended for 4.15.
>
> * Tell mac80211 when the MAC has been stripped (9000 series);
> * Tell mac80211 when the IVC has been stripped (9000 series);
> * Add 2 new PCI IDs, one for 9000 and one for 22000;
> * Fix a queue hang due during ROC.
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Kalle Valo
prev parent reply other threads:[~2017-12-07 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 14:37 pull-request: iwlwifi 2017-12-05 Luca Coelho
2017-12-07 13:52 ` 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=877etyve66.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).