From: John Hubbard <jhubbard@nvidia.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Vitaly Wool" <vitaly.wool@konsulko.se>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Bjorn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Onur Özkan" <work@onurozkan.dev>
Subject: Re: [PATCH v2] rust: rbtree: add immutable cursor
Date: Wed, 10 Sep 2025 12:40:27 -0700 [thread overview]
Message-ID: <e49f9e6c-69ee-4ec1-bcc8-3a60fda9a7be@nvidia.com> (raw)
In-Reply-To: <CANiq72=ex8zJx+KZTV5eRoqkYE=PUkbG5TTvOJo5cXTtd7b1Fg@mail.gmail.com>
On 9/9/25 7:50 PM, Miguel Ojeda wrote:
> On Wed, Sep 10, 2025 at 3:09 AM John Hubbard <jhubbard@nvidia.com> wrote:
>>
>> Interesting. I know the topic of rustc minimum version (1.78 right now)
>> has been discussed a lot, but I'm somehow still confused about how this
>> works, on nova for example.
>>
>> The &raw feature requires rustc 1.82.0. So I thought we couldn't use
>> it. But clearly we can...right?
>>
>> So confused. Please help. :)
>
> Please see what I have at this subpage:
>
> https://rust-for-linux.com/unstable-features
>
> I hope that helps!
>
Hi Miguel!
It leaves unanswered, the question of whether (and how) to use something
like the &raw feature, which requires Rust 1.82.0, given that the
stated min Rust version is 1.78.
Is there some sort of exception to the "min Rust version"? I haven't
figured out where that is written down.
thanks,
--
John Hubbard
next prev parent reply other threads:[~2025-09-10 19:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 14:02 Vitaly Wool
2025-09-08 8:47 ` Alice Ryhl
2025-09-08 9:06 ` Danilo Krummrich
2025-09-08 9:21 ` Miguel Ojeda
2025-09-08 10:22 ` Alice Ryhl
2025-09-08 11:13 ` Miguel Ojeda
2025-09-08 11:15 ` Miguel Ojeda
2025-09-10 1:09 ` John Hubbard
2025-09-10 2:50 ` Miguel Ojeda
2025-09-10 19:40 ` John Hubbard [this message]
2025-09-10 19:42 ` Danilo Krummrich
2025-09-11 2:33 ` Alexandre Courbot
2025-09-12 23:31 ` John Hubbard
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=e49f9e6c-69ee-4ec1-bcc8-3a60fda9a7be@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=vitaly.wool@konsulko.se \
--cc=work@onurozkan.dev \
/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®