From: Kalle Valo <kvalo@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-fixes 2019-07-30
Date: Wed, 31 Jul 2019 14:58:10 +0300 [thread overview]
Message-ID: <87sgqmpga5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190730171210.16570-1-johannes@sipsolutions.net> (Johannes Berg's message of "Tue, 30 Jul 2019 19:12:09 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> Hi Kalle,
>
> Resending, with all sign-offs again ... sorry, that's because Luca
> handled the previous part and then I just added stuff.
>
> Please pull and let me know if there's any problem.
>
> Thanks,
> johannes
>
>
>
> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
>
> Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git tags/iwlwifi-fixes-for-kvalo-2019-07-30
>
> for you to fetch changes up to 71b256f8f7a5c09810d2c3ed6165629c2cc0a652:
>
> iwlwifi: mvm: fix a use-after-free bug in iwl_mvm_tx_tso_segment (2019-07-30 18:34:32 +0200)
>
> ----------------------------------------------------------------
> We have a lot of fixes, most of them are also applicable to stable.
> Notably:
> * fix use-after-free issues
> * fix DMA mapping API usage errors
> * fix frame drop occurring due to reorder buffer handling in
> RSS in certain conditions
> * fix rate scale locking issues
> * disable TX A-MSDU on older NICs as it causes problems and was
> never supposed to be supported
> * new PCI IDs
> * GEO_TX_POWER_LIMIT API issue that many people were hitting
>
> ----------------------------------------------------------------
Thanks, looks good now. Pulled.
--
Kalle Valo
prev parent reply other threads:[~2019-07-31 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 17:12 pull-request: iwlwifi-fixes 2019-07-30 Johannes Berg
2019-07-31 11:58 ` 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=87sgqmpga5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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