From: "Michael Büsch" <m@bues.ch>
To: Alessio Ferri <alessio.ferri@mythread.it>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: b43: multiple parens bugs and double CORDIC_FIXED
Date: Thu, 6 Aug 2026 14:34:46 +0200 [thread overview]
Message-ID: <20260806143446.397b3f7d@barney> (raw)
In-Reply-To: <20260806104802.147ff076@DELL-MOBILE03.ad.smart.it>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On Thu, 6 Aug 2026 10:48:02 +0200
Alessio Ferri <alessio.ferri@mythread.it> wrote:
> I developed a tool to capture io traces of proprietary wl driver by
> hooking on its io accessors and then started to check mainline against
> the captured trace, i already spotted 3 bugs:
> I'll send patches in a few days once i verified them on hardware, do
> you see any problems with the capture & compare approach?
Great. Nice findings.
Please feel free to proceed with testing and sending patches.
--
Michael Büsch
https://bues.ch/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-08-06 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:48 b43: multiple parens bugs and double CORDIC_FIXED Alessio Ferri
2026-08-06 12:34 ` Michael Büsch [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=20260806143446.397b3f7d@barney \
--to=m@bues.ch \
--cc=alessio.ferri@mythread.it \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@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