All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Boris Brezillon" <boris.brezillon@collabora.com>,
	"Steven Price" <steven.price@arm.com>,
	"Liviu Dudau" <liviu.dudau@arm.com>,
	"Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: dri-devel@lists.freedesktop.org, kernel@collabora.com
Subject: Re: [PATCH v2 0/2] drm/panthor: Fix support for sync-only jobs
Date: Wed, 3 Jul 2024 09:47:09 +0200	[thread overview]
Message-ID: <20240703094709.09fb2124@collabora.com> (raw)
In-Reply-To: <20240703071640.231278-1-boris.brezillon@collabora.com>

On Wed,  3 Jul 2024 09:16:38 +0200
Boris Brezillon <boris.brezillon@collabora.com> wrote:

> Hello,
> 
> Here are two relatively trivial fixes for bugs found while woking
> on the Vulkan implementation, where NULL CS are needed to implement
> VkQueue synchronization.
> 
> Regards,
> 
> Boris
> 
> v2:
> - Fix a UAF bug in the second patch
> 
> Boris Brezillon (2):
>   drm/panthor: Don't check the array stride on empty uobj arrays
>   drm/panthor: Fix sync-only jobs

Queued to drm-misc-next.

> 
>  drivers/gpu/drm/panthor/panthor_drv.c   |  6 ++--
>  drivers/gpu/drm/panthor/panthor_sched.c | 44 ++++++++++++++++++-------
>  include/uapi/drm/panthor_drm.h          |  5 +++
>  3 files changed, 41 insertions(+), 14 deletions(-)
> 


      parent reply	other threads:[~2024-07-03  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03  7:16 [PATCH v2 0/2] drm/panthor: Fix support for sync-only jobs Boris Brezillon
2024-07-03  7:16 ` [PATCH v2 1/2] drm/panthor: Don't check the array stride on empty uobj arrays Boris Brezillon
2024-07-03  7:16 ` [PATCH v2 2/2] drm/panthor: Fix sync-only jobs Boris Brezillon
2024-07-03  7:47 ` Boris Brezillon [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=20240703094709.09fb2124@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=adrian.larumbe@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@collabora.com \
    --cc=liviu.dudau@arm.com \
    --cc=steven.price@arm.com \
    /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.