From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Michael Büsch" <m@bues.ch>, "Joshua Peisach" <jpeisach@ubuntu.com>
Cc: "Alessio Ferri" <alessio.ferri@mythread.it>,
<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 19:13:58 -0400 [thread overview]
Message-ID: <DIN19EEVA93R.2R8BXOUKWJ0GA@ubuntu.com> (raw)
In-Reply-To: <20260519215244.2a0d2b29@barney>
On Tue May 19, 2026 at 3:52 PM EDT, Michael Büsch wrote:
> On Tue, 19 May 2026 15:32:44 -0400
> "Joshua Peisach" <jpeisach@ubuntu.com> wrote:
>
>> 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.
>
> Why?
>
>> 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",
>
> Sure. That's why I ask about the development methods used.
>
>> and now we are going to have a *LLM* work on this?
>
> I don't care whether code was generated with an LLM or not.
> What matters is the development methods used.
Fair enough. And it was tested anyway :) sorry for any perceived
arrogance.
I would tag Reviewed-by but I don't have a script to check the tables
(there probably is somewhere... it's a personal problem - a "skill
issue" as I sometimes like to call it).
-Josh
WARNING: multiple messages have this Message-ID (diff)
From: "Joshua Peisach" <jpeisach@ubuntu.com>
To: "Michael Büsch" <m@bues.ch>, "Joshua Peisach" <jpeisach@ubuntu.com>
Cc: "Alessio Ferri" <alessio.ferri@mythread.it>,
<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 19:13:58 -0400 [thread overview]
Message-ID: <DIN19EEVA93R.2R8BXOUKWJ0GA@ubuntu.com> (raw)
In-Reply-To: <20260519215244.2a0d2b29@barney>
On Tue May 19, 2026 at 3:52 PM EDT, Michael Büsch wrote:
> On Tue, 19 May 2026 15:32:44 -0400
> "Joshua Peisach" <jpeisach@ubuntu.com> wrote:
>
>> 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.
>
> Why?
>
>> 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",
>
> Sure. That's why I ask about the development methods used.
>
>> and now we are going to have a *LLM* work on this?
>
> I don't care whether code was generated with an LLM or not.
> What matters is the development methods used.
Fair enough. And it was tested anyway :) sorry for any perceived
arrogance.
I would tag Reviewed-by but I don't have a script to check the tables
(there probably is somewhere... it's a personal problem - a "skill
issue" as I sometimes like to call it).
-Josh
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
next prev parent reply other threads:[~2026-05-19 23:14 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
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 [this message]
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=DIN19EEVA93R.2R8BXOUKWJ0GA@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.