From: Johannes Berg <johannes@sipsolutions.net>
To: Johan Hovold <johan@kernel.org>, Kalle Valo <kvalo@kernel.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mac80211/ath11k regression in next-20220720
Date: Fri, 22 Jul 2022 09:54:57 +0200 [thread overview]
Message-ID: <0a400422546112e91e087ce285ec5a532193ada3.camel@sipsolutions.net> (raw)
In-Reply-To: <YtpXNYta924al1Po@hovoldconsulting.com>
On Fri, 2022-07-22 at 09:52 +0200, Johan Hovold wrote:
> Hi,
>
> After moving from next-20220714 to next-20220720, ath11k stopped
> working here and instead spits out a bunch of warnings (see log below).
>
> I noticed that this series from Johannes was merged in that period:
>
> https://lore.kernel.org/all/20220713094502.163926-1-johannes@sipsolutions.net/
>
> but can't say for sure that it's related. I also tried adding the
> follow-up fixes from the mld branch:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/?h=mld
>
> but it didn't seem to make any difference.
>
> Any ideas about what might be going on here?
>
We think the "fix" is this:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?h=mld&id=dd5a559d8e90fdb9424e0580b91702c5838928dc
Do you want to try it?
Note that if that fixes it, it's still a bug in the driver, but one that
you'd otherwise not hit.
Anyway I'll do some tree shuffling today and get that in.
johannes
next prev parent reply other threads:[~2022-07-22 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:52 mac80211/ath11k regression in next-20220720 Johan Hovold
2022-07-22 7:54 ` Johannes Berg [this message]
2022-07-22 8:05 ` Johan Hovold
2022-07-22 8:06 ` Johannes Berg
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=0a400422546112e91e087ce285ec5a532193ada3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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=netdev@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