From: Danilo Krummrich <dakr@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alice Ryhl <aliceryhl@google.com>, Greg KH <greg@kroah.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the drm-rust tree with the driver-core.current tree
Date: Fri, 12 Sep 2025 09:57:48 +0200 [thread overview]
Message-ID: <420eb7d1-466b-4901-b847-e1972ccccfeb@kernel.org> (raw)
In-Reply-To: <20250912120159.1d6518cc@canb.auug.org.au>
On 9/12/25 4:01 AM, Stephen Rothwell wrote:
> diff --cc MAINTAINERS
> index 5bcaa26029f2,8a11e6c5dd80..000000000000
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@@ -7263,18 -7251,20 +7276,20 @@@ F: include/linux/dma-mapping.
> F: include/linux/swiotlb.h
> F: kernel/dma/
>
> - DMA MAPPING HELPERS DEVICE DRIVER API [RUST]
> + DMA MAPPING & SCATTERLIST API [RUST]
> -M: Abdiel Janulgue <abdiel.janulgue@gmail.com>
> M: Danilo Krummrich <dakr@kernel.org>
> +R: Abdiel Janulgue <abdiel.janulgue@gmail.com>
> R: Daniel Almeida <daniel.almeida@collabora.com>
> R: Robin Murphy <robin.murphy@arm.com>
> R: Andreas Hindborg <a.hindborg@kernel.org>
> L: rust-for-linux@vger.kernel.org
> S: Supported
> W: https://rust-for-linux.com
> -T: git https://github.com/Rust-for-Linux/linux.git alloc-next
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
> F: rust/helpers/dma.c
> + F: rust/helpers/scatterlist.c
> F: rust/kernel/dma.rs
> + F: rust/kernel/scatterlist.rs
> F: samples/rust/rust_dma.rs
>
> DMA-BUF HEAPS FRAMEWORK
Looks good, thanks!
prev parent reply other threads:[~2025-09-12 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 2:01 linux-next: manual merge of the drm-rust tree with the driver-core.current tree Stephen Rothwell
2025-09-12 7:57 ` 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=420eb7d1-466b-4901-b847-e1972ccccfeb@kernel.org \
--to=dakr@kernel.org \
--cc=aliceryhl@google.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.