public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simona Vetter <simona.vetter@ffwll.ch>
To: Philipp Stanner <phasta@kernel.org>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Maintain spsc_queue through drm_sched
Date: Fri, 24 Oct 2025 13:45:41 +0200	[thread overview]
Message-ID: <aPtm5UD4tfVBJzSh@phenom.ffwll.local> (raw)
In-Reply-To: <20251024081459.164634-2-phasta@kernel.org>

On Fri, Oct 24, 2025 at 10:15:00AM +0200, Philipp Stanner wrote:
> Back in the day a specialized lockless queue was designed solely for the
> DRM GPU Scheduler: spsc_queue. This queue's only user is drm_sched, and
> there is no dedicated maintainer entry for the queue.
> 
> Add the spsc_queue header to the DRM GPU Scheduler MAINTAINERS' section.
> 
> Signed-off-by: Philipp Stanner <phasta@kernel.org>

Acked-by: Simona Vetter <simona.vetter@ffwll.ch>

> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5889df9de210..efafe2b3517c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8580,6 +8580,7 @@ S:	Supported
>  T:	git https://gitlab.freedesktop.org/drm/misc/kernel.git
>  F:	drivers/gpu/drm/scheduler/
>  F:	include/drm/gpu_scheduler.h
> +F:	include/drm/spsc_queue.h
>  
>  DRM GPUVM
>  M:	Danilo Krummrich <dakr@kernel.org>
> -- 
> 2.49.0
> 

-- 
Simona Vetter
Software Engineer
http://blog.ffwll.ch

  reply	other threads:[~2025-10-24 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24  8:15 [PATCH] MAINTAINERS: Maintain spsc_queue through drm_sched Philipp Stanner
2025-10-24 11:45 ` Simona Vetter [this message]
2025-10-27 12:45   ` Philipp Stanner

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=aPtm5UD4tfVBJzSh@phenom.ffwll.local \
    --to=simona.vetter@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.org \
    --cc=simona@ffwll.ch \
    /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