[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h6kpf9am.fsf@metaspace.dk>
Date: Mon, 11 Dec 2023 09:09:22 +0100
From: "Andreas Hindborg (Samsung)" <nmi@...aspace.dk>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Benno Lossin <benno.lossin@...ton.me>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Alice Ryhl <aliceryhl@...gle.com>,
Jonathan Corbet <corbet@....net>,
Vincent Guittot <vincent.guittot@...aro.org>,
rust-for-linux@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: rust: Clarify that 'rustup override' applies to
build directory
Thanks for fixing this Viresh!
Viresh Kumar <viresh.kumar@...aro.org> writes:
> diff --git a/Documentation/rust/quick-start.rst b/Documentation/rust/quick-start.rst
> index f382914f4191..dee787f92d26 100644
> --- a/Documentation/rust/quick-start.rst
> +++ b/Documentation/rust/quick-start.rst
> @@ -33,14 +33,17 @@ A particular version of the Rust compiler is required. Newer versions may or
> may not work because, for the moment, the kernel depends on some unstable
> Rust features.
>
> -If ``rustup`` is being used, enter the checked out source code directory
> -and run::
> +If ``rustup`` is being used, enter the kernel build directory and run::
>
> rustup override set $(scripts/min-tool-version.sh rustc)
How about just specifying the path here:
rustup override set --path=<build-dir> $(scripts/min-tool-version.sh rustc)
Best regards,
Andreas
Powered by blists - more mailing lists