From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Mike Rapoport <rppt@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Christian Brauner <brauner@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>,
Dan Williams <dan.j.williams@intel.com>,
Theodore Ts'o <tytso@mit.edu>, Sasha Levin <sashal@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] [v2] Documentation: Provide guidelines for tool-generated content
Date: Mon, 10 Nov 2025 15:00:54 -0500 [thread overview]
Message-ID: <20251110-spiffy-intelligent-cockle-efde1e@lemur> (raw)
In-Reply-To: <20251110145405.5bc87cc5@gandalf.local.home>
On Mon, Nov 10, 2025 at 02:54:05PM -0500, Steven Rostedt wrote:
> Probably no difference. I would guess the real liability is for those that
> use AI to submit patches. With the usual disclaimers of IANAL, I'm assuming
> that when you place your "Signed-off-by", you are stating that you have the
> right to submit this code. If it comes down that you did not have the right
> to submit the code, the original submitter is liable.
And if the lawyers come back and say that the submitter is not liable, what's
to prevent someone from copypasting actual copyrighted code from a proprietary
source and adding a "Generated-by: Chat j'ai-pété" line to absolve themselves?
-K
next prev parent reply other threads:[~2025-11-10 20:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251105231514.3167738-1-dave.hansen@linux.intel.com>
2025-11-10 7:43 ` Vlastimil Babka
2025-11-10 8:58 ` Christian Brauner
2025-11-10 16:08 ` Dave Hansen
2025-11-10 17:25 ` Laurent Pinchart
2025-11-10 17:41 ` Dave Hansen
2025-11-10 17:44 ` Linus Torvalds
2025-11-10 17:56 ` Luck, Tony
2025-11-10 18:39 ` Mike Rapoport
2025-11-10 19:05 ` Linus Torvalds
2025-11-10 19:18 ` H. Peter Anvin
2025-11-10 19:36 ` Linus Torvalds
2025-11-10 19:54 ` Steven Rostedt
2025-11-10 20:00 ` Konstantin Ryabitsev [this message]
2025-11-10 20:25 ` Steven Rostedt
2025-11-10 21:21 ` James Bottomley
2025-11-10 21:42 ` Steven Rostedt
2025-11-10 21:52 ` Luck, Tony
2025-11-10 22:07 ` James Bottomley
2025-11-10 23:16 ` Theodore Ts'o
2025-11-11 9:35 ` Lorenzo Stoakes
2025-11-11 13:08 ` Theodore Ts'o
2025-11-10 17:46 ` Steven Rostedt
[not found] ` <11eaf7fa-27d0-4a57-abf0-5f24c918966c@lucifer.local>
2025-11-10 11:15 ` Lorenzo Stoakes
[not found] ` <103ee61c-f958-440c-af73-1cf3600d10fd@intel.com>
2025-11-10 16:51 ` Lorenzo Stoakes
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=20251110-spiffy-intelligent-cockle-efde1e@lemur \
--to=konstantin@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--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