Re: [PATCH RESEND wireless-next 00/18] wifi: Add Seamless Mobility Domain (SMD) AP support

[Paolo Abeni <pabeni@redhat.com>]

On 9/9/26 2:20 AM, Jeff Johnson wrote:
> On 9/8/2026 1:27 PM, Johannes Berg wrote:
>> On Tue, 2026-09-08 at 13:20 -0700, Jakub Kicinski wrote:
>>> On Tue, 08 Sep 2026 21:57:52 +0200 Johannes Berg wrote:
>>>> On Tue, 2026-09-08 at 21:51 +0200, Johannes Berg wrote:
>>>>> On Tue, 2026-09-08 at 12:50 -0700, Jakub Kicinski wrote:  
>>>>>> On Tue,  8 Sep 2026 22:39:28 +0530 Pooventhiran G wrote:  
>>>>>> Why are you sending this To: core networking maintainers.
>>>>>> This is wireless code, what do we know.
>>>>>> Drop the core maintainers and netdev@ going forward please.  
>>>>>
>>>>> They have patch 1 but I already told them a long time ago that was
>>>>> completely broken, I don't know why this is happening ...  
>>>
>>> Ah, missed the skb extension. Obvious AI slop. Fun times.
>>
>> "Look Mom, I can push a button, I'm an engineer now!"
>>
>> Do we have rules? I'm currently refusing to read anything that has an AI
>> written commit message ... at the very least.
>>
>> While I was on vacation the AI sloperators were arguing with each other
>> on the wireless list:
>> https://lore.kernel.org/linux-wireless/20260827074442.826644@enxio.de/
>>
>> Can I ban those email addresses somehow?
> Apologies for the AI-like commit messages. Those are at my prompting since I
> want these patches to be understandable by folks who may not know or
> understand the underlying details of SMD roaming so I requested they contain
> enough detail that referencing the spec should not be necessary.
> 
> AFAIK none of this code is AI generated. But it has been AI reviewed
> internally by multiple models.
> 
> /jeff

FTR, in case you intend to continue this work, skb extensions are not
for free. In fact increasing it's size may cause regression for all
workloads using them, which in turn will likely be not be acceptable.

See:

https://lore.kernel.org/netdev/73331a07-46a3-4349-98b1-b388bcd783d0@redhat.com/

/P