lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9d5d1caf-5c3c-4c58-92dc-10f73694ec0e@oss.qualcomm.com>
Date: Fri, 19 Dec 2025 13:58:53 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Konrad Dybcio <konradybcio@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
        Alex Gaynor <alex.gaynor@...il.com>, 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>, Georgi Djakov <djakov@...nel.org>,
        Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
        Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
        Marijn Suijten <marijn.suijten@...ainline.org>,
        linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
        linux-pm@...r.kernel.org
Subject: Re: [PATCH 0/2] Add initial interconnect (icc_path) Rust abstractions

On 7/24/25 5:55 PM, Miguel Ojeda wrote:
> On Thu, Jul 24, 2025 at 2:36 PM Konrad Dybcio
> <konrad.dybcio@....qualcomm.com> wrote:
>>
>> Regarding the users, I don't have any specific promises on a consumer
>> of these abstractions in a short term, although the ICC API is rather
>> common (especially across the major arm-based SoCs), so it shouldn't be
>> long before someone needs it.
> 
> In general, abstractions cannot be added unless there is a known user
> that is coming upstream (or developed in-tree over time, like Nova and
> Tyr).
> 
> There is also the "Rust reference driver" approach/exception to help C
> maintainers bootstrap the Rust side, which you may be able to take
> advantage of:
> 
>     https://rust-for-linux.com/rust-reference-drivers
> 
> At the end of the day, it depends on the particular case and the
> maintainers, of course.
> 
> I hope that helps.

I don't quite recall why I ended up sending it as-is, but thanks for your
(and all others') insight!

I may revisit this series one day, unless someone needs ICC bindings first,
then feel free to take it over.

Konrad

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ