Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Liam R. Howlett" <liam@infradead.org>, Jonathan Corbet <corbet@lwn.net>
Cc: 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 07:57:44 -0400	[thread overview]
Message-ID: <a6898b221ef656a053352e41cf8fd130ce434d60.camel@HansenPartnership.com> (raw)
In-Reply-To: <sg6yidkiqfwegabxwkrcb2dhlfkqjquwyad75xqd4j7w7o7gtx@eh6czm5aoxuy>

On Thu, 2026-07-16 at 16:23 -0400, Liam R. Howlett wrote:
> On 26/07/16 12:36PM, Jonathan Corbet wrote:
> > Sasha Levin <sashal@kernel.org> writes:
> > 
> > > On Thu, Jul 16, 2026 at 09:09:27AM -0600, Jonathan Corbet wrote:
> > > > The use of LLMs in the development process appears to be a
> > > > clear theme for the upcoming summit.  On top of what others
> > > > have already suggested, I think we may want to consider these
> > > > questions:
> > > > 
> > > > - Do we want to continue naming specific LLMs in the Assisted-
> > > > by tags, or  put something more generic?  I *think* that this
> > > > thread:
> > > > 
> > > >   
> > > > https://lore.kernel.org/all/20260701-work-coding-assistants-v1-1-a20a94d1d606@kernel.org/
> > > > 
> > > >  reached a consensus that "Assisted-by: LLM" was better than
> > > > what we require now, but it might be good to ratify that in
> > > > this setting.
> > > 
> > > So originally I've added the full name of the tool and LLM
> > > because there was interest in a later audit of the tools to
> > > determine how useful (or useless) some of the tools are.
> > > 
> > > If those folks aren't interested in doing so anymore, then sure -
> > > we can drop it.
> > > 
> > > But... I find it difficult to see the point of having the tag if
> > > we do that.
> > 
> > Folks like Greg have, in the recent past, said that it is useful
> > even without specific product-name information:
> > 
> >  
> > https://lore.kernel.org/all/2026070227-payroll-eradicate-8f66@gregkh/
> > 
> 
> There are a few classes of LLM users, but as more and more people are
> using LLM, the usefulness of this tag is converging on zero.

It's not just about whether you find it useful, it's also about whether
it has utility to the project history.  Remember the purpose of the
original signed-off-by tag was to track copyright origin in case of
another SCO like allegation.  Given the current US Copyright position
on generative AI

https://www.copyright.gov/newsnet/2025/1060.html

Whether AI is used or not affects the copyright status of the patch. 
Therefore it is a fairly vital piece of information to preserve, even
if the current advice changes over time.

Regards,

James

  parent reply	other threads:[~2026-07-17 11:57 UTC|newest]

Thread overview: 39+ 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-17 14:25       ` Mark Brown
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-18  9:26           ` Takashi Iwai
2026-07-19  9:29             ` Mauro Carvalho Chehab
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 [this message]
2026-07-17 15:53         ` Liam R. Howlett
2026-07-17 18:12           ` James Bottomley
2026-07-17 18:27             ` Dan Carpenter
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

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=a6898b221ef656a053352e41cf8fd130ce434d60.camel@HansenPartnership.com \
    --to=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