From: Al Viro <viro@zeniv.linux.org.uk>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sasha Levin <sashal@kernel.org>, Kees Cook <kees@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
corbet@lwn.net, workflows@vger.kernel.org, josh@joshtriplett.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] docs: submitting-patches: (AI?) Tool disclosure tag
Date: Fri, 25 Jul 2025 18:45:34 +0100 [thread overview]
Message-ID: <20250725174534.GY2580412@ZenIV> (raw)
In-Reply-To: <aINvLgwaKZsKOibE@gallifrey>
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...
next prev parent reply other threads:[~2025-07-25 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 17:54 linux
2025-07-24 19:07 ` Konstantin Ryabitsev
2025-07-24 20:45 ` Kees Cook
2025-07-24 21:06 ` Laurent Pinchart
2025-07-24 21:12 ` Dr. David Alan Gilbert
2025-07-24 21:20 ` Kees Cook
2025-07-24 23:45 ` Steven Rostedt
2025-07-24 23:54 ` Kees Cook
2025-07-25 0:55 ` Dr. David Alan Gilbert
2025-07-25 1:06 ` Sasha Levin
2025-07-25 1:20 ` Dr. David Alan Gilbert
2025-07-25 1:52 ` Sasha Levin
2025-07-25 2:02 ` Steven Rostedt
2025-07-25 2:39 ` Sasha Levin
2025-07-25 11:29 ` Dr. David Alan Gilbert
2025-07-25 11:37 ` Laurent Pinchart
2025-07-25 11:49 ` Dr. David Alan Gilbert
2025-07-25 17:45 ` Al Viro [this message]
2025-07-25 22:40 ` Sasha Levin
2025-07-25 23:29 ` Dr. David Alan Gilbert
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=20250725174534.GY2580412@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=workflows@vger.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