mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 22:57:45 +0200	[thread overview]
Message-ID: <20261023225745.696eef3c@barney> (raw)
In-Reply-To: <CAKxU2N_1XgjVPdSrCMYzZx4Rb6yjgEe7kBZYyG4RASyBv5BtMw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Fri, 23 Oct 2026 13:44:44 -0700
Rosen Penev <rosenp@gmail.com> wrote:

> All code is tested on an Asus RT-N16. It runs on non-coherent MIPS.

Ok.

Describe your development process in human language during patch submission.
What has been tested?
What has not been tested?
What was wrong?
What has been fixed?
Why is this needed?
Why do we need bidirectional DMA and most important why wasn't it necessary before?

AI is great for code generation, bug finding, etc.
But for patch submission, pull requests and commit messages it's absolutely unusable.
Please don't do it.
Write your commit messages manually, please.

Please make your commit message be to the point and easy to review.
And please slow the process down.
You don't need to submit patches right away. Keep them in a queue and STABILIZE them LOCALLY.

Please do a little bit of research whom to To and Cc. There are scripts for that.

Thanks a lot.

-- 
Michael Büsch
https://bues.ch/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-10-23 20:58 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 [this message]
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=20261023225745.696eef3c@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®