rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: daniel.almeida@collabora.com, a.hindborg@kernel.org,
	linux-kernel@vger.kernel.org, dakr@redhat.com,
	airlied@redhat.com, miguel.ojeda.sandonis@gmail.com,
	wedsonaf@gmail.com, Abdiel Janulgue <abdiel.janulgue@gmail.com>
Subject: [PATCH v3 0/2] Add dma coherent allocator abstraction
Date: Mon,  4 Nov 2024 11:06:32 +0200	[thread overview]
Message-ID: <20241104090711.3000818-1-abdiel.janulgue@gmail.com> (raw)

This series adds support for the dma coherent allocator.

Changes since v2:
- Fixed missing header for generating the bindings.

Changes since v1:
- Fix missing info in commit log where EOVERFLOW is used
- Restrict the dma coherent allocator to numeric types for now for valid
  behaviour.
- Build slice dynamically.

Abdiel Janulgue (2):
  rust: error: Add EOVERFLOW
  rust: add dma coherent allocator abstraction.

 rust/bindings/bindings_helper.h |   1 +
 rust/kernel/dma.rs              | 165 ++++++++++++++++++++++++++++++++
 rust/kernel/error.rs            |   1 +
 rust/kernel/lib.rs              |   1 +
 4 files changed, 168 insertions(+)
 create mode 100644 rust/kernel/dma.rs


base-commit: ae7851c29747fa3765ecb722fe722117a346f988
-- 
2.43.0


             reply	other threads:[~2024-11-04  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  9:06 Abdiel Janulgue [this message]
2024-11-04  9:06 ` [PATCH v3 1/2] rust: error: Add EOVERFLOW Abdiel Janulgue
2024-11-04  9:06 ` [PATCH v3 2/2] rust: add dma coherent allocator abstraction Abdiel Janulgue
2024-11-04  9:31   ` Alice Ryhl
2024-11-04  9:36     ` Abdiel Janulgue
2024-11-04 10:00       ` Alice Ryhl
2024-11-04 10:31         ` Abdiel Janulgue

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=20241104090711.3000818-1-abdiel.janulgue@gmail.com \
    --to=abdiel.janulgue@gmail.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@redhat.com \
    --cc=dakr@redhat.com \
    --cc=daniel.almeida@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).