From: Sasha Levin <sashal@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Kalle Valo <quic_kvalo@quicinc.com>,
Kalle Valo <kvalo@kernel.org>,
quic_jjohnson@quicinc.com, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.4 03/10] Revert "wifi: ath11k: Enable threaded NAPI"
Date: Wed, 23 Aug 2023 14:03:51 -0400 [thread overview]
Message-ID: <ZOZKB5J+Xwu+41Xw@sashalap> (raw)
In-Reply-To: <ZOTcGEfqsBkWugAa@hovoldconsulting.com>
On Tue, Aug 22, 2023 at 06:02:32PM +0200, Johan Hovold wrote:
>On Tue, Aug 22, 2023 at 07:30:53AM -0400, Sasha Levin wrote:
>> From: Kalle Valo <quic_kvalo@quicinc.com>
>>
>> [ Upstream commit d265ebe41c911314bd273c218a37088835959fa1 ]
>>
>> This reverts commit 13aa2fb692d3717767303817f35b3e650109add3.
>>
>> This commit broke QCN9074 initialisation:
>>
>> [ 358.960477] ath11k_pci 0000:04:00.0: ce desc not available for wmi command 36866
>> [ 358.960481] ath11k_pci 0000:04:00.0: failed to send WMI_STA_POWERSAVE_PARAM_CMDID
>> [ 358.960484] ath11k_pci 0000:04:00.0: could not set uapsd params -105
>>
>> As there's no fix available let's just revert it to get QCN9074 working again.
>>
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217536
>> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
>> Signed-off-by: Kalle Valo <kvalo@kernel.org>
>> Link: https://lore.kernel.org/r/20230720151444.2016637-1-kvalo@kernel.org
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>This commit break machines like the Lenovo ThinkPad X13s so please do
>not backport until this has been resolved:
>
> https://lore.kernel.org/lkml/20230809073432.4193-1-johan+linaro@kernel.org
I'll drop it for now, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-08-23 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 11:30 [PATCH AUTOSEL 6.4 01/10] clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 02/10] vmbus_testing: fix wrong python syntax for integer value comparison Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 03/10] Revert "wifi: ath11k: Enable threaded NAPI" Sasha Levin
2023-08-22 16:02 ` Johan Hovold
2023-08-23 18:03 ` Sasha Levin [this message]
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 04/10] Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning on GCC 12" Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 05/10] net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit boundaries Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 06/10] net: annotate data-races around sk->sk_{rcv|snd}timeo Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 07/10] net: usb: qmi_wwan: add Quectel EM05GV2 Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 08/10] wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1() Sasha Levin
2023-08-22 11:30 ` [PATCH AUTOSEL 6.4 09/10] powerpc/powermac: Use early_* IO variants in via_calibrate_decr() Sasha Levin
2023-08-22 11:31 ` [PATCH AUTOSEL 6.4 10/10] x86/hyperv: add noop functions to x86_init mpparse functions Sasha Levin
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=ZOZKB5J+Xwu+41Xw@sashalap \
--to=sashal@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=johan@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_kvalo@quicinc.com \
--cc=stable@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