[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <774D098D-9FEC-45CC-8645-A6E5A7BEB4DF@collabora.com>
Date: Fri, 7 Feb 2025 10:25:08 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: 崔光博 <2407018371@...com>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Alice Ryhl <aliceryhl@...gle.com>,
a.hindborg@...nel.org,
alex.gaynor@...il.com,
benno.lossin@...ton.me,
bjorn3_gh@...tonmail.mco,
boqun.feng@...il.com,
boris.brezillon@...labora.com,
gary@...yguo.net,
gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org,
ojeda@...nel.org,
rafael@...nel.org,
robh@...nel.org,
rust-for-linux@...r.kernel.org,
tmgross@...ch.edu
Subject: Re: [PATCH v6 2/3] rust: io: mem: add a generic iomem abstraction
Sorry, didn’t find time to reply yesterday,
>
> That's two different things here. Miguel questions whether the comment is
> correct. And I think it's not, they are indeed exposed.
>
Yes, I said “not exposed”, but in truth I meant “you can’t use it”, as shown by
the build_error being triggered.
My bad. I will fix the wording so that it’s clear in the next iteration.
— Daniel
Powered by blists - more mailing lists