From: "Linux kernel regression tracking (#update)" <regressions@leemhuis.info>
To: Bryan O'Donoghue <pure.logic@nexus-software.ie>,
Alexander Wetzel <alexander@wetzel-home.de>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
linux-kernel@vger.kernel.org, johannes.berg@intel.com,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org
Subject: Re: ieee80211_handle_wake_tx_queue and dynamic ps regression
Date: Fri, 13 Jan 2023 13:17:58 +0100 [thread overview]
Message-ID: <be49babe-46ff-5a80-21db-c8b4562bc17a@leemhuis.info> (raw)
In-Reply-To: <aace6523-0941-903e-6b80-399dc1cfc751@nexus-software.ie>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 10.01.23 20:35, Bryan O'Donoghue wrote:
> On 10/01/2023 15:43, Alexander Wetzel wrote:
>> Looks like the the commit
>> https://patchwork.kernel.org/project/linux-wireless/patch/20221230121850.218810-1-alexander@wetzel-home.de/
>> has a good chance to solve the issue:
> [..]
>> Does that make sense? And more crucial, is the patch fixing that for you?
>
> Ok works for me.
In that case:
#regzbot fix: wifi: mac80211: Proper mark iTXQs for resumption
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-01-13 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19015168-c747-17b7-f0ae-9d2ee27d221c@linaro.org>
2023-01-10 12:44 ` ieee80211_handle_wake_tx_queue and dynamic ps regression Bryan O'Donoghue
2023-01-10 14:47 ` Bryan O'Donoghue
2023-01-10 15:23 ` Alexander Wetzel
2023-01-10 15:43 ` Alexander Wetzel
2023-01-10 19:35 ` Bryan O'Donoghue
2023-01-13 12:17 ` Linux kernel regression tracking (#update) [this message]
2023-01-10 16:06 ` Bryan O'Donoghue
2023-01-10 13:08 ` Linux kernel regression tracking (Thorsten Leemhuis)
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=be49babe-46ff-5a80-21db-c8b4562bc17a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alexander@wetzel-home.de \
--cc=bryan.odonoghue@linaro.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pure.logic@nexus-software.ie \
--cc=regressions@lists.linux.dev \
/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).