From nobody Tue Dec 16 07:40:17 2025 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 2421EC6FD18 for ; Tue, 18 Apr 2023 21:44:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232944AbjDRVoh (ORCPT ); Tue, 18 Apr 2023 17:44:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59086 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232331AbjDRVoe (ORCPT ); Tue, 18 Apr 2023 17:44:34 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 173E34C1B; Tue, 18 Apr 2023 14:44:33 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A40F662E5F; Tue, 18 Apr 2023 21:44:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1C49DC4339C; Tue, 18 Apr 2023 21:44:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1681854272; bh=PEJ21Jum+8RkGBoHGrrQC2DdRUmxtG2ZVlTGGrsyUic=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=tGuC/XLSVrXqEujsgvql/IRDy7Wrla/QrdVy0fr/0AWv5wVdnDVzTwltqM2r6UAp1 SHhLoQi+2DPpMhYOj7XxFJPfoThVJp2dLZJyQAaOzhbFHg4SFVmHaf/CjxjRjYX9gP pWdRfYiVWMcQkdCg67cWSGPiTEmoEUATcGkaXV7TwzZXIBdT1XCbEu5l0k+Hu90Jkb tqLimTXcw1PPyiMqtAy/DoZMd/aAs03Zl5A4R+g0+AbKk3gx6pgtNwgiBLaV1uVi4w gQh574fNpYajHkjPlYnP2KgWCEXHhJdLRtmtIHtgkBCDNjtWzLVzIKByKzmGP+E1WQ aw0/pxTQu1GMA== From: Miguel Ojeda To: Miguel Ojeda , Wedson Almeida Filho , Alex Gaynor Cc: Boqun Feng , Gary Guo , =?UTF-8?q?Bj=C3=B6rn=20Roy=20Baron?= , Benno Lossin , Josh Stone , William Brown , Georgy Yakovlev , Jan Alexander Steffens , rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org, patches@lists.linux.dev Subject: [PATCH 1/3] rust: alloc: clarify what is the upstream version Date: Tue, 18 Apr 2023 23:43:45 +0200 Message-Id: <20230418214347.324156-2-ojeda@kernel.org> In-Reply-To: <20230418214347.324156-1-ojeda@kernel.org> References: <20230418214347.324156-1-ojeda@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" It may be unclear for readers which upstream Rust version these files are based on. They may be unaware that they are intended to match the minimum (and only, so far) supported version of Rust in the kernel. Thus clarify it. Signed-off-by: Miguel Ojeda Reviewed-by: Benno Lossin Reviewed-by: Bj=C3=B6rn Roy Baron Reviewed-by: Gary Guo Reviewed-by: Martin Rodriguez Reboredo --- rust/alloc/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/rust/alloc/README.md b/rust/alloc/README.md index c89c753720b5..eb6f22e94ebf 100644 --- a/rust/alloc/README.md +++ b/rust/alloc/README.md @@ -10,6 +10,9 @@ upstream. In general, only additions should be performed = (e.g. new methods). Eventually, changes should make it into upstream so that, at some point, this fork can be dropped from the kernel tree. =20 +The Rust upstream version on top of which these files are based matches +the output of `scripts/min-tool-version.sh rustc`. + =20 ## Rationale =20 --=20 2.40.0