From: Johannes Berg <johannes@sipsolutions.net>
To: syzbot <syzbot@kernel.org>,
syzkaller-bugs@googlegroups.com, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, syzbot@lists.linux.dev,
Slawomir Stepien <sst@poczta.fm>,
Krystian Kaniewski <krystianmkaniewski@gmail.com>
Subject: sysbot AI patches and wireless
Date: Thu, 06 Aug 2026 09:57:13 +0200 [thread overview]
Message-ID: <3b6c46b6d79f3a0e0ded2967db3cfd469314b05c.camel@sipsolutions.net> (raw)
In-Reply-To: <068e46b5-0c88-4432-959a-b9400d9691ee@mail.kernel.org>
Hi,
> See https://goo.gle/syzbot-ai-patches for information about AI-generated patches.
> You can comment on the patch as usual, syzbot will try to address
> the comments and send a new version of the patch if necessary.
I'm going to state, for the record, that I'm going to make judicious use
of ability to ignore patches, and apply it to pretty much all syzbot-AI-
generated patches unless a 3-second review says "obviously right".
In particular, I will absolutely *not* "comment on the patches as usual"
and argue with an LLM that can bullshit out code faster than another
computer can even deliver it to me by email.
Whoever is currently pretending to be the human in the loop *absolutely*
needs to think about the patches, and if that's happening it's probably
no longer an AI-generated-sent-by-syzbot but you're going to rewrite it
and send it properly.
(IOW: get lost, syzbot)
johannes
next prev parent reply other threads:[~2026-08-06 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 7:45 [PATCH] wifi: mac80211: prevent destroying non-TDLS stations in TDLS operations syzbot
2026-08-06 7:57 ` Johannes Berg [this message]
2026-08-06 8:20 ` sysbot AI patches and wireless Aleksandr Nogikh
2026-08-06 10:15 ` Johannes Berg
2026-08-06 11:38 ` Slawomir Stepien
2026-08-06 14:49 ` Johannes Berg
2026-08-06 23:30 ` Hillf Danton
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=3b6c46b6d79f3a0e0ded2967db3cfd469314b05c.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=krystianmkaniewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sst@poczta.fm \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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