[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250725174534.GY2580412@ZenIV>
Date: Fri, 25 Jul 2025 18:45:34 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: "Dr. David Alan Gilbert" <linux@...blig.org>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Sasha Levin <sashal@...nel.org>, Kees Cook <kees@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
corbet@....net, workflows@...r.kernel.org, josh@...htriplett.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] docs: submitting-patches: (AI?) Tool disclosure tag
On Fri, Jul 25, 2025 at 11:49:02AM +0000, Dr. David Alan Gilbert wrote:
> > Except from a copyright point of view. The situation is quite clear for
> > deterministic code generation, it's less so for LLMs.
>
> As long as you'd acknowledged the use of the LLM in all cases, it seems to
> me right to say to what degree you use it (i.e. the 1..3) above.
> I think even most people worried about copright issues would worry
> less if an LLM had just told you about a problem (1) and you fixed it.
> (Although obviously IANAL)
s/told you about a problem/told you that <location> has triggered some
heuristics and might or might not be worth looking into/, really...
Powered by blists - more mailing lists