[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nxor1_d-b7=eH9mObddyJ5mbW5jStGSamGq+jL17ebqw@mail.gmail.com>
Date: Tue, 20 Jan 2026 22:02:25 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alexandre Courbot <acourbot@...dia.com>
Cc: Dirk Behme <dirk.behme@...bosch.com>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Yury Norov <yury.norov@...il.com>,
John Hubbard <jhubbard@...dia.com>, Alistair Popple <apopple@...dia.com>,
Joel Fernandes <joelagnelf@...dia.com>, Timur Tabi <ttabi@...dia.com>, Edwin Peer <epeer@...dia.com>,
Eliot Courtney <ecourtney@...dia.com>, Daniel Almeida <daniel.almeida@...labora.com>,
Steven Price <steven.price@....com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/6] rust: add `bitfield!` macro
On Tue, Jan 20, 2026 at 2:20 PM Alexandre Courbot <acourbot@...dia.com> wrote:
>
> We can avoid the feature altogether, but it is of course more convenient
> if we can infer these generic parameters when possible. But if you
> prefer we eschew that, no big deal. One can even argue the code is more
> readable that way.
As long as it builds (infers) properly with the minimum version, it
seems fine to me to use.
> I haven't found how to enable it for doctests anyway - maybe this is not
> currently doable?
"World-available" features are enabled for the entire kernel,
including doctests (this is what I meant in my reply to Dirk).
We list them in the `rust_allowed_features` line in `scripts/Makefile.build`.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists