Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Johan Hovold <johan@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
	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 10:06:55 +0200	[thread overview]
Message-ID: <9b2b7ae17008881d9ee35163aeaa183604f5364a.camel@sipsolutions.net> (raw)
In-Reply-To: <YtpaQXhM5wuz4Zbq@hovoldconsulting.com>

On Fri, 2022-07-22 at 10:05 +0200, Johan Hovold wrote:
> > 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?
> 
> Thanks for the quick reply. And yes, that fixes the problem.

OK great, thanks for checking!

> I apparently failed to apply all commits from that mld branch, but this
> one alone fixes it.

OK, I'll check later.

> > Note that if that fixes it, it's still a bug in the driver, but one that
> > you'd otherwise not hit.
> 
> Yeah, those warnings looked like secondary issues if that's what you're
> referring to?

No, I mean there are legitimate cases where override==true, and then the
driver breaks. It's just uncommon (I think perhaps only specific
userspace [debug] configurations), but it could happen.

johannes

      reply	other threads:[~2022-07-22  8:07 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
2022-07-22  8:05   ` Johan Hovold
2022-07-22  8:06     ` Johannes Berg [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=9b2b7ae17008881d9ee35163aeaa183604f5364a.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