From: "Christian König" <christian.koenig@amd.com>
To: "Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: DMA BUFFER SHARING FRAMEWORK: tighten F: matches
Date: Wed, 16 Sep 2026 15:30:07 +0200 [thread overview]
Message-ID: <a51b4181-f102-4820-b5c1-af9cb3d9b77f@amd.com> (raw)
In-Reply-To: <20260916-maint-dma-buf-v1-1-0f8d6c5bf1cd@kernel.org>
On 9/16/26 15:21, Mike Rapoport (Microsoft) wrote:
> F: include/linux/*fence.h
>
> in "DMA BUFFER SHARING FRAMEWORK" entry matches include/linux/kfence.h
> although that header has nothing to do with dma-buf.
>
> Replace it with explicit 'include/linux/dma-fence.h'.
>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Acked-by: Christian König <christian.koenig@amd.com>
Thanks a lot that was on my TODO list for an eternity as well!
Regards,
Christian
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c2414447892c2..656bc5ed8d2ba 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7688,7 +7688,7 @@ T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
> F: Documentation/driver-api/dma-buf.rst
> F: Documentation/userspace-api/dma-buf-alloc-exchange.rst
> F: drivers/dma-buf/
> -F: include/linux/*fence.h
> +F: include/linux/dma-fence.h
> F: include/linux/dma-buf.h
> F: include/linux/dma-buf/
> F: include/linux/dma-resv.h
>
> ---
> base-commit: fd73f4a6659897191fa0d40695fe370925dd3780
> change-id: 20260916-maint-dma-buf-3311abfdc90e
>
> --
> Sincerely yours,
> Mike.
>
prev parent reply other threads:[~2026-09-16 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:21 Mike Rapoport (Microsoft)
2026-09-16 13:30 ` 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=a51b4181-f102-4820-b5c1-af9cb3d9b77f@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--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
all inboxes | Powered by JetHome®