From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mslow1.mail.gandi.net (mslow1.mail.gandi.net [217.70.178.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BBD3B70 for ; Wed, 7 Jul 2021 13:46:13 +0000 (UTC) Received: from relay8-d.mail.gandi.net (unknown [217.70.183.201]) by mslow1.mail.gandi.net (Postfix) with ESMTP id 24113C688A for ; Wed, 7 Jul 2021 13:39:10 +0000 (UTC) Received: (Authenticated sender: alexandre.belloni@bootlin.com) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 17F7F1BF210; Wed, 7 Jul 2021 13:39:01 +0000 (UTC) Date: Wed, 7 Jul 2021 15:39:00 +0200 From: Alexandre Belloni To: Miguel Ojeda Cc: Sasha Levin , Linus Walleij , Leon Romanovsky , ksummit@lists.linux.dev Subject: Re: [TECH TOPIC] Rust for Linux Message-ID: References: Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 06/07/2021 23:50:51+0200, Miguel Ojeda wrote: > On Tue, Jul 6, 2021 at 10:47 PM Sasha Levin wrote: > > > > I strongly disagree. If we have abstractions for a particular subsystem > > all it means that someone at some point did that work, nothing more than > > that. > > > > That someone might have moved on, working elsewhere, retired, etc, and > > those abstractions are living orphaned in the kernel. > > That problem is orthogonal to Rust/C. I already acknowledged that if > you want to refactor Rust code, you will need some bare minimum Rust > knowledge -- there is no way around that, for any language. > > And indeed, a second language introduces downsides like this -- this > is also acknowledged in the original RFC. > > What I am saying is that, in the beginning (when most kernel > developers are not accustomed to Rust), a solution would be that > subsystem maintainers could step up and help those doing a refactor > that touches their Rust code. We also discussed a bit of this in the > original LKML discussion back in April; and we also offered ourselves > (the Rust support folks) to help as much as we can if anybody is > having issues on the Rust side. So that means that if a subsystem maintainer doesn't know Rust, Rust code should not be merge in that subsystem at all. -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com