From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable <stable@kernel.org>
Subject: Re: [PATCH net] nfc: pn533: properly drop the usb interface reference on disconnect
Date: Wed, 25 Feb 2026 06:30:31 -0800 [thread overview]
Message-ID: <2026022550-routing-grain-6886@gregkh> (raw)
In-Reply-To: <20260224174203.405d0a93@kernel.org>
On Tue, Feb 24, 2026 at 05:42:03PM -0800, Jakub Kicinski wrote:
> On Mon, 23 Feb 2026 12:28:30 +0100 Greg Kroah-Hartman wrote:
> > Assisted-by: gkh_clanker_2000
>
> I feel like this tag completely validates my position that the whole
> Assisted-by tag is nonsense. Random "Person X's bot" tags cannot help
> any cross-kernel research into problems with AI coding tools. And all
> of us, employees of AI-pilled companies, are routinely using a whole
> slew of AI-backed tools on our kernel submissions. Which cannot be
> practically captured by such tags, since they are evolving rapidly.
>
> Are you okay with me stripping these when I apply your patches?
> Or do you strongly prefer to keep them?
No objection from stripping it at all. My tooling has no feelings
whatsoever and are not trying to justify an inflated market validation
with advertising their use and so will not even notice. :)
I added it to show that I did have "help" in finding the location for
where to do this type of fix, I didn't just pull it out of thin air on
my own.
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-25 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 11:28 [PATCH net] nfc: pn533: properly drop the usb interface reference on disconnect Greg Kroah-Hartman
2026-02-24 9:17 ` Simon Horman
2026-02-25 14:31 ` Greg Kroah-Hartman
2026-02-25 18:57 ` Simon Horman
2026-02-25 1:42 ` Jakub Kicinski
2026-02-25 14:30 ` Greg Kroah-Hartman [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=2026022550-routing-grain-6886@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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