From: "Christian König" <christian.koenig@amd.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>,
Maxime Ripard <mripard@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Remove obsolete file entry in DMA BUFFER SHARING FRAMEWORK
Date: Thu, 9 Apr 2026 13:49:55 +0200 [thread overview]
Message-ID: <8975e6a9-89fe-4bb9-96ed-cb2522202b92@amd.com> (raw)
In-Reply-To: <20260408100819.458347-1-lukas.bulwahn@redhat.com>
On 4/8/26 12:08, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit 25bd73562941 ("dma: contiguous: Turn heap registration logic
> around") removes the file include/linux/dma-buf/heaps/cma.h, which is the
> only file in include/linux/dma-buf/.
>
> Hence, there is no file matching the file entry include/linux/dma-buf/ in
> the MAINTAINERS section DMA BUFFER SHARING FRAMEWORK.
>
> Remove this obsolete file entry in DMA BUFFER SHARING FRAMEWORK.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 10d12b51b1f6..77c0fc7ede03 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7561,7 +7561,6 @@ F: Documentation/userspace-api/dma-buf-alloc-exchange.rst
> F: drivers/dma-buf/
> F: include/linux/*fence.h
> F: include/linux/dma-buf.h
> -F: include/linux/dma-buf/
> F: include/linux/dma-resv.h
> F: rust/helpers/dma-resv.c
> K: \bdma_(?:buf|fence|resv)\b
> --
> 2.53.0
>
prev parent reply other threads:[~2026-04-09 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 10:08 [PATCH] MAINTAINERS: Remove obsolete file entry in DMA BUFFER SHARING FRAMEWORK Lukas Bulwahn
2026-04-09 8:16 ` Maxime Ripard
2026-04-09 11:49 ` Christian König [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=8975e6a9-89fe-4bb9-96ed-cb2522202b92@amd.com \
--to=christian.koenig@amd.com \
--cc=iommu@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=m.szyprowski@samsung.com \
--cc=mripard@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sumit.semwal@linaro.org \
/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