From: Alan Stern <stern@rowland.harvard.edu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Petko Manolov <petkan@nucleusys.com>, stable <stable@kernel.org>
Subject: Re: [PATCH net] net: usb: pegasus: validate USB endpoints
Date: Mon, 23 Feb 2026 10:02:01 -0500 [thread overview]
Message-ID: <ed6ad3d0-e46e-413e-9db7-1c788c8a2dbe@rowland.harvard.edu> (raw)
In-Reply-To: <2026022352-dried-sputter-eba9@gregkh>
On Mon, Feb 23, 2026 at 03:54:30PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Feb 23, 2026 at 09:39:52AM -0500, Alan Stern wrote:
> > BTW, what is gkh_clanker_2000?
>
> A hacked up system of tools/scripts I'm running here to find stuff like
> "take this previously applied commit that fixed a problem, does the same
> pattern need to be also done anywhere else in the tree"? It finds a lot
> of stuff and then I sift through it and see if anything is actually real
> or not and if so, make up a patch for it. It was my "merge window is
> giving me a respite from reviewing patches" hobby project this past
> week.
>
> Now if I was really good, I could turn the output into a coccinelle
> script, as this is just simple patterns.
It's a little surprising that nobody has asked an AI to do this sort of
thing yet (as far as I know). It's hard to say whether the results
would be better than you get with your hacked-up system of
tools/scripts, but it might be.
Alan Stern
next prev parent reply other threads:[~2026-02-23 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 12:58 Greg Kroah-Hartman
2026-02-23 14:39 ` Alan Stern
2026-02-23 14:54 ` Greg Kroah-Hartman
2026-02-23 15:02 ` Alan Stern [this message]
2026-02-26 3:00 ` patchwork-bot+netdevbpf
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=ed6ad3d0-e46e-413e-9db7-1c788c8a2dbe@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petkan@nucleusys.com \
--cc=stable@kernel.org \
/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®