[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aOZpwUD50MwSBycB@casper.infradead.org>
Date: Wed, 8 Oct 2025 14:40:17 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Onur Özkan <work@...rozkan.dev>,
rust-for-linux@...r.kernel.org, ojeda@...nel.org,
alex.gaynor@...il.com, boqun.feng@...il.com, gary@...yguo.net,
bjorn3_gh@...tonmail.com, lossin@...nel.org, tmgross@...ch.edu,
dakr@...nel.org, linux-kernel@...r.kernel.org, acourbot@...dia.com,
airlied@...il.com, simona@...ll.ch,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
tzimmermann@...e.de, corbet@....net, lyude@...hat.com,
linux-doc@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 2/4] rust: xarray: abstract `xa_alloc`
On Wed, Oct 08, 2025 at 01:04:11PM +0000, Alice Ryhl wrote:
> > + limit: Range<u32>,
>
> The Range type is inclusive/exclusive but xa_limit is
> inclusive/inclusive. They should match to avoid confusion.
... and xa_limit is inclusive at the top end to be sure that we can
actually allocate 2^32-1. Or does Range handle that by using 0 to mean
that 2^32-1 is allowed?
>
Powered by blists - more mailing lists