From: "Michael Büsch" <m@bues.ch>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"open list:B43 WIRELESS DRIVER" <b43-dev@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH wireless] wifi: b43: map the RX buffers DMA_BIDIRECTIONAL
Date: Fri, 23 Oct 2026 23:39:53 +0200 [thread overview]
Message-ID: <20261023233953.65c45360@barney> (raw)
In-Reply-To: <CAKxU2N9i6Dn1yKmd-_9DvET6P_GNctTywWgOBXYd2tWoWKY=Sg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
On Fri, 23 Oct 2026 14:21:27 -0700
Rosen Penev <rosenp@gmail.com> wrote:
>> Why do we need bidirectional DMA and most important why wasn't it necessary before?
>Because the codepath is not fatal. One or two duplicated frames. Big deal.
I do not understand what this means.
Please explain this in human language.
Why is the code wrong?
Why did it work for almost two decades?
Why does it need to change?
Please explain it to a human being with code examples and failure scenarios that are understandable.
It is completely Ok, if it *does* need to change.
I am just asking for an explanation that is not AI generated.
If you want me to read it, it should not be too much for you to type it down.
> > Write your commit messages manually, please.
> I've been burned by this many times before where maintainers ask me to
> reword or mention something. It's not practical and wastes everyone's
> time, which is why I'm almost banned from netdev.
I'm sorry, you are wrong.
This is not how software development works.
If you can't explain what you submit, I am going to NAK everything.
(even if I don't have the formal power anymore, see below)
> Do note this is an orphaned driver.
Yes, I know. I am the former maintainer.
>I expect [..] Fixes: to get in a bit easier.
No.
Fixes need to be explained to avoid regressions.
--
Michael Büsch
https://bues.ch/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-10-23 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 19:06 Rosen Penev
2026-10-23 20:14 ` Michael Büsch
2026-10-23 20:41 ` Michael Büsch
2026-10-23 20:44 ` Rosen Penev
2026-10-23 20:57 ` Michael Büsch
2026-10-23 21:21 ` Rosen Penev
2026-10-23 21:39 ` 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=20261023233953.65c45360@barney \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rosenp@gmail.com \
/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
all inboxes | Powered by JetHome®