Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp299238ybt; Thu, 9 Jul 2020 23:28:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx4jTRXalCIIihwp2rqsnZxxnk9EtNd9wvHAyttTU979Kz4TNBLpBolvIqhx+c79xs5QOJB X-Received: by 2002:a05:6402:2d7:: with SMTP id b23mr63772559edx.145.1594362532596; Thu, 09 Jul 2020 23:28:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594362532; cv=none; d=google.com; s=arc-20160816; b=LvZQ3geHPjZsZXuPbLEiuSKWHRw2pbusZu+xVZVWsDZD/Vyy24q50/TizSpG6RC+lk SDLya/mFanFE/n9Gx53hS8FF2tKuB0TLauio97PEqIZgceCqmAztVAp0vOlNESrMBimJ LbQriH3vPNOr1fNVx/SdghNB0VJoxggsMxe97DxkgASfFT2Q+a78+aTDqjWdUBJs/+Nq c+xX0azwbJvLyn/mWuuvekOZ7BM0UpeZGQw5FwKYeXQDRsCOAb2MSRoib9B3qZN8SECE LJiIyiHlhp0FXG0Zx0DBGGNIXPxMS6dJI6XBP3wV6VtzZIsZJBUqjYLCsqqTEBZ9wjkt LdzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=jGCrylmCQqWFEmn7xDprKKOC/kaItevjLJlVqcOzlwI=; b=t/iKgDXVSwOA6jo48sFqTEedwJtieK3zqMwzUnStoGTFE9xq9e15toh7cDA4jXSJ3W 3xkuw0TLlGAYAkZbd6XjJyiooNd/B9kysRTl6Lwf1oVXgaw8qP4XTKgrRbMt9otJQbYE 4mVBqBpAHTyLDtyq0HApPGbl1DQq5IxFhj2A3iB51YlT+2SuKM4i2zKwgbsyp324W8X/ ta05nOlBJfCBzi4xs7FGSuGouxnyzznvN43bHSQyhQTj8QsOcqQ5lywBCYjfvdu9vAX8 V+rZsUviAILLGUbtCov/T8iR+JW9cr+2YvH3Vqz74oa29bLzwo89oM9En1jV1WzEfupl MW3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=txiTPIjP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id du7si4500006ejc.341.2020.07.09.23.28.28; Thu, 09 Jul 2020 23:28:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=txiTPIjP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726201AbgGJG17 (ORCPT + 99 others); Fri, 10 Jul 2020 02:27:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:41238 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725851AbgGJG17 (ORCPT ); Fri, 10 Jul 2020 02:27:59 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3EA672072E; Fri, 10 Jul 2020 06:27:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1594362478; bh=H0eG/s1lyQ6sGKykTdhmRGHO9rgBoUeZDW5jJ3sAsmw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=txiTPIjP7EudtwFFn2YASO02jf6cgq/0rtL5MoTYHZAIdyuF4w0LA9lL93NoFVq9Z LZGcvlkTF3hScD2f6C2C5Wea2oJGht379bfES+OFi4ulUp5FNwovbNxDFVnkPqwjH4 hBnrMQ+ZJy7bLi8Q3iET28YzUrjvicIXswH/LVe4= Date: Fri, 10 Jul 2020 08:28:03 +0200 From: Greg KH To: Nick Desaulniers Cc: alex.gaynor@gmail.com, geofft@ldpreload.com, jbaublitz@redhat.com, Masahiro Yamada , Linus Torvalds , Miguel Ojeda , Josh Triplett , Steven Rostedt , LKML , clang-built-linux Subject: Re: Linux kernel in-tree Rust support Message-ID: <20200710062803.GA1071395@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 09, 2020 at 11:41:47AM -0700, Nick Desaulniers wrote: > Hello folks, > I'm working on putting together an LLVM "Micro Conference" for the > upcoming Linux Plumbers Conf > (https://www.linuxplumbersconf.org/event/7/page/47-attend). It's not > solidified yet, but I would really like to run a session on support > for Rust "in tree." I suspect we could cover technical aspects of > what that might look like (I have a prototype of that, was trivial to > wire up KBuild support), but also a larger question of "should we do > this?" or "how might we place limits on where this can be used?" > > Question to folks explicitly in To:, are you planning on attending plumbers? > > If so, would this be an interesting topic that you'd participate in? Yes, I'll be there. thanks, greg k-h