From: Dave Hansen <dave.hansen@intel.com>
To: Christian Brauner <brauner@kernel.org>,
tech-board-discuss@lists.linux.dev
Cc: linux-kernel@vger.kernel.org,
ksummit-discuss@lists.linuxfoundation.org,
christianvanbrauner@gmail.com
Subject: Re: LLM based rewrites
Date: Mon, 9 Mar 2026 09:05:38 -0700 [thread overview]
Message-ID: <6d39e290-e25f-4b27-8e36-f1ec0b74118b@intel.com> (raw)
In-Reply-To: <20260307-clean-room-6118793eb175@brauner>
On 3/7/26 12:49, Christian Brauner wrote:
> I'm not asking for a legal analysis. I'm mostly looking for reassurance
> that we as the kernel community and our representatives have an eye on
> this. I find this quite worrisome.
Let's say someone did this for the kernel and released it under a more
permissive license. Let's also ignore whether this is legally or morally
naughty or nice for the moment.
Any way you slice it, they'd start with a gigantic Linux-like code base
and effectively zero people to work on it. It would _effectively_ be a
big kernel fork. Maybe it would be different because it's got a more
permissive license. Linus would be proved wrong after all these years
and contributors would flock to the new codebase, throwing off the
chains of the evil GPLv2 that kept Linux from being successful.
Mainline has survived quite a few kernel forks. There would have to be
something pretty darn compelling about this new fork. Considering that
license taste is about as universal as vi/emacs taste, I doubt the
license itself would be compelling on its own. Maybe the new kernel
would be 100% rust? Maybe it would be more friendly to LLM maintenance?
Either way, Magic 8 Ball says: "Concentrate and ask again". So this does
sound like a great TAB topic! ;)
next prev parent reply other threads:[~2026-03-09 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 20:49 Christian Brauner
2026-03-09 13:57 ` Steven Rostedt
2026-03-09 15:31 ` H. Peter Anvin
2026-03-09 16:16 ` Steven Rostedt
2026-03-09 16:33 ` Jonathan Corbet
2026-03-09 16:55 ` H. Peter Anvin
2026-03-09 17:09 ` H. Peter Anvin
2026-03-09 18:19 ` James Bottomley
2026-03-09 18:34 ` Steven Rostedt
2026-03-09 18:38 ` Dr. David Alan Gilbert
2026-03-09 18:54 ` James Bottomley
2026-03-10 4:52 ` Theodore Tso
[not found] ` <CAMTJT3_cVaA7aJmDa6j288-qwP3jzvM_R2pdk+XmE+1U=Sovbg@mail.gmail.com>
2026-03-10 12:47 ` Theodore Tso
2026-03-10 14:10 ` Dr. Greg
2026-03-09 16:05 ` Dave Hansen [this message]
2026-03-09 16:16 ` James Bottomley
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=6d39e290-e25f-4b27-8e36-f1ec0b74118b@intel.com \
--to=dave.hansen@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linux.dev \
/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
all inboxes | Powered by JetHome®