From: "Michael Büsch" <m@bues.ch>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org (open list:B43 WIRELESS DRIVER),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH wireless] wifi: b43: map the RX buffers DMA_BIDIRECTIONAL
Date: Fri, 23 Oct 2026 22:41:40 +0200 [thread overview]
Message-ID: <20261023224140.465903eb@barney> (raw)
In-Reply-To: <20261023221424.2722795e@barney>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
To explain this further:
- I might be wrong, but this patch looks completely bogus to me.
Why would this be bi-directional?
If this is accessed bi-directionally, there must be a bug somewhere else.
- Please provide a HUMAN WRITTEN patch description.
This is really important.
I am all for using AI for development.
Especially for such old and legacy code.
HOWEVER, there must be a human present and understanding what is being done.
Please slow down your submissions.
Think about your patches before submission.
TEST your code before submission and send evidence of your tests.
Untested code is to be rejected.
--
Michael Büsch
https://bues.ch/
On Fri, 23 Oct 2026 22:14:24 +0200
Michael Büsch <m@bues.ch> wrote:
> Quite honestly, to me this looks like a lot of AI slop is sent to b43 these days.
> Can you please slow down your submissions so that actual people get a chance to review the stuff?
> Thanks!
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-10-23 20:42 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 [this message]
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
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=20261023224140.465903eb@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®