[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fdc54cf6-5574-4061-a90e-81bd9e2f2be1@gmail.com>
Date: Wed, 26 Mar 2025 22:25:11 +0200
From: Abdiel Janulgue <abdiel.janulgue@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: a.hindborg@...nel.org, ojeda@...nel.org,
Danilo Krummrich <dakr@...nel.org>,
Daniel Almeida <daniel.almeida@...labora.com>,
Robin Murphy <robin.murphy@....com>, 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 <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>,
"open list:DMA MAPPING HELPERS DEVICE DRIVER API [RUST]"
<rust-for-linux@...r.kernel.org>, Marek Szyprowski
<m.szyprowski@...sung.com>,
"open list:DMA MAPPING HELPERS" <iommu@...ts.linux.dev>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Additional fixes for dma coherent allocator
Hi Miguel,
On 26/03/2025 22:18, Miguel Ojeda wrote:
> On Wed, Mar 26, 2025 at 9:13 PM Abdiel Janulgue
> <abdiel.janulgue@...il.com> wrote:
>>
>> Additional fixups to improve the documentation and make the read/write
>> macros return Result as suggested by Andreas Hindborg as well as support
>> for reading and writing large blocks of data.
>
> As far as I can tell, these seem improvements more than fixes -- so
> can they go through the normal process for the next cycle?
>
Sure! I'm totally fine with it.
Regards,
Abdiel
Powered by blists - more mailing lists