From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1C16AC64EC4 for ; Mon, 6 Mar 2023 19:18:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229780AbjCFTS1 (ORCPT ); Mon, 6 Mar 2023 14:18:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42012 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229932AbjCFTSV (ORCPT ); Mon, 6 Mar 2023 14:18:21 -0500 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 144796589 for ; Mon, 6 Mar 2023 11:18:08 -0800 (PST) Received: by mail-pj1-x1032.google.com with SMTP id u3-20020a17090a450300b00239db6d7d47so9685334pjg.4 for ; Mon, 06 Mar 2023 11:18:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20210112.gappssmtp.com; s=20210112; t=1678130287; h=content-transfer-encoding:mime-version:message-id:to:from:cc :in-reply-to:subject:date:from:to:cc:subject:date:message-id :reply-to; bh=PlfUVnMpAeqg74Kjt8UEOETBGNFFbOVFaXPZinB2uzA=; b=t5crri0WcTaC4dbDeFT8B1Wf41RotuxLDoQ4au4TS14bhzVMaHsw9aHDiNZ/QgfigO pIri5VdgzvPiiJjI1Fi6ly7z7LM/WBF4IOflr++3YI+qk3fjdDueo9IiFarU45YM93jy InVglw2HcfH0SVosPwcOZVudDiaF8aEsAty9SKv60VRlOJ6dbXxRUnEfnuwuksQRL+oH MjCDHAW0mtGh5caILOuIvpWpotLpNMICgWII/CmspOGryPGZRcLIX7VDlhmcKqnho09M v3nqHeyXn7TJizhYBWel17Os2plRYUMcAagxx2fq7Xno7HV5B6AU7E+r1P+9n6NyddI7 /lAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678130287; h=content-transfer-encoding:mime-version:message-id:to:from:cc :in-reply-to:subject:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PlfUVnMpAeqg74Kjt8UEOETBGNFFbOVFaXPZinB2uzA=; b=U0ObJvqQ8FoBY/Gn+e88z/eP358s8Iq7O7Sxy9ev08Ux9tC+r1vOWP0n2wHfvl9Gvz yYvwE3UVs6tuJPkkkN7dh1AYhGT80lB6vnDBBK/yZfdtIjqG1zobSQNL+R2/j16ccm0G O7gwM/e4nQvuRP2IAmJTuaKabpdnH7RXf1rBNwNzledWbNzoQfAFibXZBhOgu5J+fAcY vkLKupJRnpNDSYS4QOIA2bFXPmAbB9HD1KAjc5cWk5CAlOd5PRbaBcVdcKg//eI+7xUZ TNJdJ2VpGHBMaIsUkVgDU7lLSm8XQVPAybLjVFBMAbKnTQo7c1++zZW47VEghWTm1VeC SeCg== X-Gm-Message-State: AO0yUKVFNWs+2kx4vCBTNsT3QVd2xhtwZDmiyDGIe3LmT1YYHcT06+9u 5gAz+jRaR4nghzcDGoi0iswoPw== X-Google-Smtp-Source: AK7set+iNoJZ2cxy5qRgIoHSJ0YdyIfw0jMkr21udOVpB5izRmx1RUdTQKZ9Owwbph8LjbeyohY5Ag== X-Received: by 2002:a05:6a20:5483:b0:cc:50de:a2be with SMTP id i3-20020a056a20548300b000cc50dea2bemr13625900pzk.14.1678130287404; Mon, 06 Mar 2023 11:18:07 -0800 (PST) Received: from localhost ([50.221.140.188]) by smtp.gmail.com with ESMTPSA id d23-20020aa78697000000b005afda149679sm6782709pfo.179.2023.03.06.11.18.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Mar 2023 11:18:06 -0800 (PST) Date: Mon, 06 Mar 2023 11:18:06 -0800 (PST) X-Google-Original-Date: Mon, 06 Mar 2023 11:17:18 PST (-0800) Subject: Re: [RFC 0/2] RISC-V: enable rust In-Reply-To: CC: Conor Dooley , linux-riscv@lists.infradead.org, Conor Dooley , ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com, boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com, corbet@lwn.net, Paul Walmsley , nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com, rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev From: Palmer Dabbelt To: miguel.ojeda.sandonis@gmail.com Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: rust-for-linux@vger.kernel.org On Sat, 25 Feb 2023 00:37:29 PST (-0800), miguel.ojeda.sandonis@gmail.com wrote: > On Sat, Feb 25, 2023 at 12:18 AM Palmer Dabbelt wrote: >> >> Works for me. >> >> I've got a few other things in the pipeline for this merge window so >> this probably won't make it, but I'll dig in after that. We've got a >> bunch of Rust-types floating around Rivos as well, so with any luck >> someone else will have some time to poke around. Having a full cycle in >> linux-next is probably the right way to go for this sort of thing >> anyway, as it's likely to shake out some long-tail issues. > > Thanks a lot! That would be great. > > At least from our side, no rush. In fact, we are letting users (or > arch maintainers) to request/submit the architectures themselves as > they need/want them. It's time for the next release. IIUC there were some authorship issues here, did you guys want to re-spin this with those sorted out? I can give it a shot if you want, but I'm probably as likely to screw it up as anyone else...