All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Abdiel Janulgue <abdiel.janulgue@gmail.com>
Cc: acourbot@nvidia.com, "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Valentin Obst" <kernel@valentinobst.de>,
	"open list" <linux-kernel@vger.kernel.org>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	airlied@redhat.com, rust-for-linux@vger.kernel.org,
	"open list:DMA MAPPING HELPERS" <iommu@lists.linux.dev>,
	"Petr Tesarik" <petr@tesarici.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"Sui Jingfeng" <sui.jingfeng@linux.dev>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Michael Kelley" <mhklinux@outlook.com>
Subject: Re: [PATCH v4 0/3] Additional improvements for dma coherent allocator
Date: Mon, 23 Jun 2025 17:42:56 +0200	[thread overview]
Message-ID: <aFl2AOUQ-CKYgIn8@cassiopeiae> (raw)
In-Reply-To: <20250602085444.1925053-1-abdiel.janulgue@gmail.com>

On Mon, Jun 02, 2025 at 11:53:10AM +0300, Abdiel Janulgue wrote:

Applied to alloc-next, thanks!

> Abdiel Janulgue (3):
>   rust: dma: clarify wording and be consistent in `coherent`
>     nomenclature
>   rust: dma: convert the read/write macros to return Result

  [ Fix line length in dma_read!(). - Danilo ]

>   rust: dma: add as_slice/write functions for CoherentAllocation

  [ Fix line length and slightly reword safety comment in doc-test of
    CoherentAllocation::write(); fix formatting issue. - Danilo ]

      parent reply	other threads:[~2025-06-23 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02  8:53 [PATCH v4 0/3] Additional improvements for dma coherent allocator Abdiel Janulgue
2025-06-02  8:53 ` [PATCH v4 1/3] rust: dma: clarify wording and be consistent in `coherent` nomenclature Abdiel Janulgue
2025-06-13 12:49   ` Andreas Hindborg
2025-06-02  8:53 ` [PATCH v4 2/3] rust: dma: convert the read/write macros to return Result Abdiel Janulgue
2025-06-02  8:53 ` [PATCH v4 3/3] rust: dma: add as_slice/write functions for CoherentAllocation Abdiel Janulgue
2025-06-02 13:05   ` Alexandre Courbot
2025-06-13  9:45     ` Abdiel Janulgue
2025-06-13 10:31       ` Abdiel Janulgue
2025-06-15 12:51       ` Alexandre Courbot
2025-06-23 15:42 ` Danilo Krummrich [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=aFl2AOUQ-CKYgIn8@cassiopeiae \
    --to=dakr@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=abdiel.janulgue@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=iommu@lists.linux.dev \
    --cc=kernel@valentinobst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mhklinux@outlook.com \
    --cc=ojeda@kernel.org \
    --cc=petr@tesarici.cz \
    --cc=rdunlap@infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sui.jingfeng@linux.dev \
    --cc=tmgross@umich.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.