All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Michael Büsch" <m@bues.ch>, "Alessio Ferri" <alessio.ferri@mythread.it>
Cc: <linux-wireless@vger.kernel.org>, <b43-dev@lists.infradead.org>,
	<kvalo@kernel.org>, <linux-kernel@vger.kernel.org>,
	"b43-dev" <b43-dev-bounces@lists.infradead.org>
Subject: Re: [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support
Date: Tue, 19 May 2026 15:32:44 -0400	[thread overview]
Message-ID: <DIMWK04RLFCG.17KT0R0YCUMRW@ubuntu.com> (raw)
In-Reply-To: <20260519175812.7ce97ba1@barney>

On Tue May 19, 2026 at 11:58 AM EDT, Michael Büsch wrote:
> On Mon, 18 May 2026 03:49:33 +0200
> Alessio Ferri <alessio.ferri@mythread.it> wrote:
>
> In general this looks Ok.
> From the style I assume that this is AI generated, right?
> If so, can you tell us a bit more about the inputs used for the AI?
> What information is this implementation based on?

So... awkward question. Wasn't there just a conversation[1] about the
future development of this module, that was left off at "don't touch it
unless you're going to thouroughly test this", and now we are going to
have a *LLM* work on this?

That aside, I don't see any obvious issues in the patchset.

[1]: https://lore.kernel.org/b43-dev/DHTYJFGLKPQ0.RYJIDH2VLV3W@ubuntu.com/T/#t

WARNING: multiple messages have this Message-ID (diff)
From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Michael Büsch" <m@bues.ch>, "Alessio Ferri" <alessio.ferri@mythread.it>
Cc: <linux-wireless@vger.kernel.org>, <b43-dev@lists.infradead.org>,
	<kvalo@kernel.org>, <linux-kernel@vger.kernel.org>,
	"b43-dev" <b43-dev-bounces@lists.infradead.org>
Subject: Re: [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support
Date: Tue, 19 May 2026 15:32:44 -0400	[thread overview]
Message-ID: <DIMWK04RLFCG.17KT0R0YCUMRW@ubuntu.com> (raw)
In-Reply-To: <20260519175812.7ce97ba1@barney>

On Tue May 19, 2026 at 11:58 AM EDT, Michael Büsch wrote:
> On Mon, 18 May 2026 03:49:33 +0200
> Alessio Ferri <alessio.ferri@mythread.it> wrote:
>
> In general this looks Ok.
> From the style I assume that this is AI generated, right?
> If so, can you tell us a bit more about the inputs used for the AI?
> What information is this implementation based on?

So... awkward question. Wasn't there just a conversation[1] about the
future development of this module, that was left off at "don't touch it
unless you're going to thouroughly test this", and now we are going to
have a *LLM* work on this?

That aside, I don't see any obvious issues in the patchset.

[1]: https://lore.kernel.org/b43-dev/DHTYJFGLKPQ0.RYJIDH2VLV3W@ubuntu.com/T/#t

_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

  reply	other threads:[~2026-05-19 19:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  1:49 [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support Alessio Ferri
2026-05-18  1:49 ` Alessio Ferri
2026-05-18  1:50 ` [PATCH 1/6] b43: add d11 core revision 0x16 to id table Alessio Ferri
2026-05-18  1:50   ` Alessio Ferri
2026-05-18  1:51 ` [PATCH 2/6] b43: route d11 corerev 22 to 24-bit indirect radio access Alessio Ferri
2026-05-18  1:51   ` Alessio Ferri
2026-05-18  1:51 ` [PATCH 3/6] b43: support radio 2057 rev 8 Alessio Ferri
2026-05-18  1:51   ` Alessio Ferri
2026-05-18  1:53 ` [PATCH 4/6] b43: add IPA TX gain table for N-PHY r8 + radio 2057 r8 Alessio Ferri
2026-05-18  1:53   ` Alessio Ferri
2026-05-18  1:54 ` [PATCH 5/6] b43: add channel info " Alessio Ferri
2026-05-18  1:54   ` Alessio Ferri
2026-05-18  1:54 ` [PATCH 6/6] b43: add RF power offset " Alessio Ferri
2026-05-18  1:54   ` Alessio Ferri
2026-05-19 15:58 ` [PATCH 0/6] b43: complete N-PHY rev 8 + radio 2057 rev 8 support Michael Büsch
2026-05-19 15:58   ` Michael Büsch
2026-05-19 19:32   ` Joshua Peisach [this message]
2026-05-19 19:32     ` Joshua Peisach
2026-05-19 19:52     ` Michael Büsch
2026-05-19 19:52       ` Michael Büsch
2026-05-19 23:13       ` Joshua Peisach
2026-05-19 23:13         ` Joshua Peisach
2026-05-19 21:02   ` Alessio Ferri
2026-05-19 21:02     ` Alessio Ferri
2026-05-20 11:06     ` Johannes Berg
2026-05-20 11:06       ` Johannes Berg
2026-05-20 21:25       ` Alessio Ferri
2026-05-20 21:25         ` Alessio Ferri
2026-05-20 23:16       ` Alessio Ferri
2026-05-20 23:16         ` Alessio Ferri

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=DIMWK04RLFCG.17KT0R0YCUMRW@ubuntu.com \
    --to=jpeisach@ubuntu.com \
    --cc=alessio.ferri@mythread.it \
    --cc=b43-dev-bounces@lists.infradead.org \
    --cc=b43-dev@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m@bues.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.