mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Chia-I Wu <olvaffe@gmail.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] panthor: print task pid and comm on gpu errors
Date: Thu, 24 Jul 2025 13:52:07 +0100	[thread overview]
Message-ID: <78ec8bcc-0178-4c5d-9d03-0b534bdd2231@arm.com> (raw)
In-Reply-To: <20250718063816.1452123-1-olvaffe@gmail.com>

On 18/07/2025 07:38, Chia-I Wu wrote:
> This series saves task pid and comm in panthor_group and prints task pid and
> comm on gpu errors.
> 
> v3: fix new kerneldoc warnings
> v2: save the task info in panthor_group on panthor_group_create, rather than
>     in panthor_file on panthor_open, because, when the two differ, we are more
>     interested in the task that created the group.
> 
> Chia-I Wu (3):
>   panthor: set owner field for driver fops
>   panthor: save task pid and comm in panthor_group
>   panthor: dump task pid and comm on gpu errors
> 
>  drivers/gpu/drm/panthor/panthor_drv.c   | 14 ++------
>  drivers/gpu/drm/panthor/panthor_sched.c | 43 ++++++++++++++++++++++---
>  2 files changed, 41 insertions(+), 16 deletions(-)
> 

Applied to drm-misc-next.

Thanks,
Steve


      parent reply	other threads:[~2025-07-24 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  6:38 Chia-I Wu
2025-07-18  6:38 ` [PATCH v3 1/3] panthor: set owner field for driver fops Chia-I Wu
2025-07-18  6:38 ` [PATCH v3 2/3] panthor: save task pid and comm in panthor_group Chia-I Wu
2025-07-18  6:38 ` [PATCH v3 3/3] panthor: dump task pid and comm on gpu errors Chia-I Wu
2025-07-24 12:52 ` Steven Price [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=78ec8bcc-0178-4c5d-9d03-0b534bdd2231@arm.com \
    --to=steven.price@arm.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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®