From: Dan Carpenter <error27@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: "Liam R. Howlett" <liam@infradead.org>,
Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc
Date: Fri, 17 Jul 2026 21:27:15 +0300 [thread overview]
Message-ID: <alp0A8ThbUr6uRNc@stanley.mountain> (raw)
In-Reply-To: <4adc1ace832afefd30e48f0a05b27b58d9fbd604.camel@HansenPartnership.com>
On Fri, Jul 17, 2026 at 02:12:31PM -0400, James Bottomley wrote:
> On Fri, 2026-07-17 at 11:53 -0400, Liam R. Howlett wrote:
> But the point is that whatever happens (even if nothing does) we'd have
> tags in the code base to identify most of the affected code.
The Signed-off-by rules are simple to enforce but it's impossible to
know when a patch is written by AI. It's definitely a small minority
of patches which are tagged and not "most of the affected code".
regards,
dan carpenter
next prev parent reply other threads:[~2026-07-17 18:27 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 15:09 [MAINTAINERS SUMMIT] Other LLM-related topics - tags, newcomers, etc Jonathan Corbet
2026-07-16 15:28 ` Sasha Levin
2026-07-16 16:08 ` Mark Brown
2026-07-16 16:24 ` Sasha Levin
2026-07-16 20:38 ` Laurent Pinchart
2026-07-17 14:09 ` Sasha Levin
2026-07-21 23:15 ` Laurent Pinchart
2026-07-22 0:23 ` Guenter Roeck
2026-07-17 14:25 ` Mark Brown
2026-07-21 23:58 ` Jori Koolstra
2026-07-22 0:57 ` Linus Torvalds
2026-07-22 14:20 ` Trond Myklebust
2026-07-23 14:15 ` Mark Brown
2026-07-22 17:48 ` Konstantin Ryabitsev
2026-07-22 19:15 ` Linus Torvalds
2026-07-23 0:26 ` Kees Cook
2026-07-23 13:10 ` Steven Rostedt
2026-07-23 14:30 ` Jori Koolstra
2026-07-16 18:36 ` Jonathan Corbet
2026-07-16 19:53 ` Mauro Carvalho Chehab
2026-07-16 23:59 ` Theodore Tso
2026-07-17 0:58 ` Mauro Carvalho Chehab
2026-07-17 2:27 ` Theodore Tso
2026-07-17 7:19 ` Mauro Carvalho Chehab
2026-07-19 9:01 ` Mauro Carvalho Chehab
2026-07-21 18:21 ` Mauro Carvalho Chehab
2026-07-18 9:26 ` Takashi Iwai
2026-07-19 9:29 ` Mauro Carvalho Chehab
2026-07-22 9:53 ` Takashi Iwai
2026-07-17 13:55 ` Konstantin Ryabitsev
2026-07-17 14:24 ` Andrew Lunn
2026-07-17 14:32 ` Konstantin Ryabitsev
2026-07-17 14:50 ` Andrew Lunn
2026-07-17 20:21 ` Theodore Tso
2026-07-18 12:54 ` Mauro Carvalho Chehab
2026-07-16 20:05 ` Bart Van Assche
2026-07-16 20:52 ` James Bottomley
2026-07-16 20:23 ` Liam R. Howlett
2026-07-17 7:49 ` Laurent Pinchart
2026-07-17 15:55 ` Liam R. Howlett
2026-07-17 11:57 ` James Bottomley
2026-07-17 15:53 ` Liam R. Howlett
2026-07-17 18:12 ` James Bottomley
2026-07-17 18:27 ` Dan Carpenter [this message]
2026-07-17 18:42 ` James Bottomley
2026-07-18 1:13 ` Theodore Tso
2026-07-18 3:07 ` James Bottomley
2026-07-17 14:54 ` Johannes Weiner
2026-07-17 16:09 ` Liam R. Howlett
2026-07-16 21:23 ` Theodore Tso
2026-07-17 13:59 ` Sasha Levin
2026-07-17 14:09 ` Konstantin Ryabitsev
2026-07-21 23:24 ` Jori Koolstra
2026-08-08 8:45 ` Dan Carpenter
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=alp0A8ThbUr6uRNc@stanley.mountain \
--to=error27@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=liam@infradead.org \
--cc=sashal@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