All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>
Cc: ath11k@lists.infradead.org,
	 Linux regressions mailing list <regressions@lists.linux.dev>,
	 linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] ath11k broken in v6.7
Date: Mon, 22 Jan 2024 10:24:23 +0200	[thread overview]
Message-ID: <87fryp3he0.fsf@kernel.org> (raw)
In-Reply-To: <94150b26-bdd9-49c2-82a1-26ff46c9d32a@leemhuis.info> (Linux regression tracking's message of "Mon, 22 Jan 2024 09:03:27 +0100")

"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info> writes:

> On 22.01.24 08:36, Kalle Valo wrote:
>> Kalle Valo <kvalo@kernel.org> writes:
>>> Kalle Valo <kvalo@kernel.org> writes:
>>>> Kalle Valo <kvalo@kernel.org> writes:
>>>>
>>>>> Just trying to make everyone aware because I suspect this will affect
>>>>> quite a few people: ath11k is crashing during suspend on v6.7 due to a
>>>>> mac80211 patch, more info:
>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=218364
>
> Many thx for the heads up, much appreciated. Sorry, forgot to add it to
> the tracking myself: during the merge window thing are sometimes a bit
> chaotic for myself as well. And I was head-down in rewriting some parts
> of regzbot (see below).

No worries, this was a good time to learn all this myself.

>>>>> Proposed fix:
>>>>> https://patchwork.kernel.org/project/linux-wireless/patch/20240111170629.1257217-1-benjamin@sipsolutions.net/
>>>>
>>>> The fix is now applied:
>>>>
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/?id=556857aa1d0855aba02b1c63bc52b91ec63fc2cc
>>>>
>>>> I'll try to use regzbot for the first time, let's see how it goes:
>>>>
>>>> #regzbot introduced: 0a3d898ee9a8 ^
>>>
>>> Forgot to include the bug report:
>>>
>>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218364
>
> FWIW, that usage was slightly off and not how it's supposed to be done.
> But whatever, let's ignore that. I'm reworking things currently
> slightly, as you are not the first one that slightly got mislead -- and
> the newer commands will hopefully be mire intuitive.

Just to educate myself, how should I have done it? (But feel free to
skip the question if you are busy)

>> #regzbot fix: 556857aa1d0855aba02b1c63bc52b91ec63fc2cc
>
> Great, thx. Hope it reached mainline soon. Maybe once it's there you or
> I should tell Greg to pick this up quickly for stable given that it
> apparently "might affect quite a few people".

I'll try to remember that but the thing is that I don't really follow
stable releases. I wish there would be a person who could follow stable
releases from wireless perspective and make sure everything is ok there.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-01-22  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 20:47 [regression] ath11k broken in v6.7 Kalle Valo
2024-01-19  6:34 ` Kalle Valo
2024-01-19  7:50   ` Kalle Valo
2024-01-22  7:36     ` Kalle Valo
2024-01-22  8:03       ` Linux regression tracking (Thorsten Leemhuis)
2024-01-22  8:24         ` Kalle Valo [this message]
2024-01-22 10:24           ` Thorsten Leemhuis
2024-01-29 11:33             ` Kalle Valo
2024-02-02  8:14               ` Thorsten Leemhuis
2024-02-02 10:45                 ` Kalle Valo
2024-02-02 11:29                   ` Linux regression tracking (Thorsten Leemhuis)
2024-02-02 11:34                     ` Kalle Valo

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=87fryp3he0.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.