[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72m8t2j3+XoELfYFG9ivymueOGdwpZnFhRVZ8f3Xw9ygiA@mail.gmail.com>
Date: Tue, 7 Oct 2025 19:28:31 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: Alice Ryhl <aliceryhl@...gle.com>, 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
Subject: Re: [PATCH 2/3] rust: xarray: abstract `xa_alloc_cyclic`
On Tue, Oct 7, 2025 at 7:19 PM Onur Özkan <work@...rozkan.dev> wrote:
>
> Why do we not like to use the bindings type directly?
For public APIs, we generally try to avoid exposing C types:
https://docs.kernel.org/rust/general-information.html#abstractions-vs-bindings
Sometimes it still makes sense, of course, e.g. a method may return
an inner type so that it gets used by other abstractions to call into
C. But generally we want to avoid exposing those for drivers and other
abstractions wherever possible.
Cheers,
Miguel
Powered by blists - more mailing lists