From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Luca Coelho <luca@coelho.fi>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless <linux-wireless@vger.kernel.org>, "Grumbach\,
Emmanuel" <emmanuel.grumbach@intel.com>,
johannes.hirte@datenkhaos.de, steven@uplinklabs.net,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH for v5.2] iwlwifi: mvm: disable TX-AMSDU on older NICs
Date: Thu, 25 Jul 2019 08:55:03 +0300 [thread overview]
Message-ID: <87muh2zmiw.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+ASDXPjLW+Zrf-uruCLMFGGDaJd=xYWt4tb=T_0HKP=ZnHbTQ@mail.gmail.com> (Brian Norris's message of "Wed, 24 Jul 2019 16:55:25 -0700")
Brian Norris <briannorris@chromium.org> writes:
> On Wed, Jul 3, 2019 at 4:46 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Luca Coelho <luca@coelho.fi> writes:
>> > Hi Dave,
>> >
>> > This is an important fix for a bug that has been reported by several
>> > users in bugzilla (and elsewhere). It fixes FW crashes that disrupt
>> > throughput and connectivity in general in very popular devices (Intel's
>> > WiFi 7000 and 8000 series).
>> >
>> > I know it's a bit late for v5.2, but if possible, it would be great to
>> > take this. Kalle is on vacation, so we agreed that I would send it
>> > directly to you.
>>
>> Acked-by: Kalle Valo <kvalo@codeaurora.org>
>
> 5.2 has come and gone, and I believe Kalle has awoken from vacation.
Yeah, I have sort of crawled out of my cave ;)
> Can we get this for 5.3?
Ah, this slipped through the cracks. Thanks for pointing it out. I now
took this patch from Luca and assigned to myself in patchwork and I'll
queue this for v5.3.
https://patchwork.kernel.org/patch/11029027/
--
Kalle Valo
prev parent reply other threads:[~2019-07-25 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 8:10 [PATCH for v5.2] iwlwifi: mvm: disable TX-AMSDU on older NICs Luca Coelho
2019-07-03 8:14 ` Luca Coelho
2019-07-03 11:45 ` Kalle Valo
2019-07-24 23:55 ` Brian Norris
2019-07-25 5:55 ` 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=87muh2zmiw.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes.hirte@datenkhaos.de \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=steven@uplinklabs.net \
/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).