mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Huacai Chen <chenhuacai@kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>, WANG Rui <wangrui@loongson.cn>,
	rust-for-linux@vger.kernel.org, loongarch@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] docs: rust: quick-start: Add another way to install
Date: Thu, 4 Sep 2025 11:55:29 +0800	[thread overview]
Message-ID: <4f8a98af-d5ec-faac-27bb-2d1b0ec7ed77@loongson.cn> (raw)
In-Reply-To: <CANiq72m0HO91gFcVuH3kPz6b6fZ_vrbO3BGmb3DpyhuRnvGkeQ@mail.gmail.com>

On 2025/9/3 下午6:11, Miguel Ojeda wrote:
> On Wed, Sep 3, 2025 at 11:53 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>>
>> It seems that the latest version of rustc is not compatible, in order to
> 
> This is only in nightly Rust -- we have a couple commits in -next that
> make Rust >= 1.91 work. Could you please try those? i.e. starting at
> 8851e27d2cb9 ("rust: support Rust >= 1.91.0 target spec"). They should
> land in e.g. -rc5.

OK, will try.

> Regarding `rustup`: we could link to the install instructions, but I
> don't think it is a good idea to replicate a particular `curl` line
> that could change upstream (e.g. the domain changing hands),
> especially one that installs something on the fly.

I will drop this patch in the next version.

Thanks,
Tiezhu


  reply	other threads:[~2025-09-04  3:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03  9:53 [RFC PATCH 0/3] Fix objtool warnings with RUST on LoongArch Tiezhu Yang
2025-09-03  9:53 ` [RFC PATCH 1/3] docs: rust: quick-start: Add another way to install Tiezhu Yang
2025-09-03 10:11   ` Miguel Ojeda
2025-09-04  3:55     ` Tiezhu Yang [this message]
2025-09-03  9:53 ` [RFC PATCH 2/3] LoongArch: Make LTO case independent in Makefile Tiezhu Yang
2025-09-03  9:53 ` [RFC PATCH 3/3] LoongArch: Handle table jump option for RUST Tiezhu Yang
2025-09-03 10:28   ` Miguel Ojeda
2025-09-04  3:57     ` Tiezhu Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f8a98af-d5ec-faac-27bb-2d1b0ec7ed77@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=wangrui@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®