From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Abdiel Janulgue <abdiel.janulgue@gmail.com>
Cc: rust-for-linux@vger.kernel.org, aliceryhl@google.com,
daniel.almeida@collabora.com, a.hindborg@kernel.org,
dakr@redhat.com, airlied@redhat.com, wedsonaf@gmail.com,
a.hindborg@samsung.com
Subject: Re: [PATCH v4 0/2] Add dma coherent allocator abstraction
Date: Wed, 6 Nov 2024 10:47:17 +0200 [thread overview]
Message-ID: <2cf513bd-456e-4000-a295-8e8147798db5@gmail.com> (raw)
In-Reply-To: <CANiq72kPvMQJwCxm_cAcNqtCL1rMYKR_0JR3O+O3+1zUiOdrZQ@mail.gmail.com>
On 05/11/2024 13:23, Miguel Ojeda wrote:
> On Tue, Nov 5, 2024 at 11:47 AM Abdiel Janulgue
> <abdiel.janulgue@gmail.com> wrote:
>>
>> This series adds support for the dma coherent allocator.
>
> Shouldn't this Cc the DMA mapping helpers subsystem/maintainers? (also
> please Cc the rest of the Rust subsystem maintainers/reviewers too).
>
Thanks for the reminder with this guideline. Will do so in next update.
/Abdiel
> Thanks!
>
> Cheers,
> Miguel
>
prev parent reply other threads:[~2024-11-06 8:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 10:46 [PATCH v4 0/2] Add dma coherent allocator abstraction Abdiel Janulgue
2024-11-05 10:46 ` [PATCH v4 1/2] rust: error: Add EOVERFLOW Abdiel Janulgue
2024-11-05 10:46 ` [PATCH v4 2/2] rust: add dma coherent allocator abstraction Abdiel Janulgue
2024-11-05 11:23 ` Miguel Ojeda
2024-11-06 8:47 ` Abdiel Janulgue
2024-11-06 10:21 ` Dirk Behme
2024-11-06 11:25 ` Miguel Ojeda
2024-11-06 16:40 ` Daniel Almeida
2024-11-07 13:01 ` Abdiel Janulgue
2024-11-09 23:42 ` Daniel Almeida
2024-11-11 10:48 ` Abdiel Janulgue
2024-11-11 12:55 ` Andreas Hindborg
2024-11-11 12:59 ` Abdiel Janulgue
2024-11-05 11:23 ` [PATCH v4 0/2] Add " Miguel Ojeda
2024-11-06 8:47 ` Abdiel Janulgue [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cf513bd-456e-4000-a295-8e8147798db5@gmail.com \
--to=abdiel.janulgue@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=dakr@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).