public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH 0/3] drm/xe/rtp: OA register whitelist fixes
Date: Tue, 14 Apr 2026 12:28:03 -0300	[thread overview]
Message-ID: <87se8xwoho.fsf@intel.com> (raw)
In-Reply-To: <20260414035244.741342-1-ashutosh.dixit@intel.com>

Ashutosh Dixit <ashutosh.dixit@intel.com> writes:

> Ashutosh Dixit (3):
>   drm/xe/rtp: Don't whitelist OA status registers
>   drm/xe/rtp: Don't whitelist OA head pointer registers
>   drm/xe/rtp: Fix offset alignment for MERT WHITELIST_OA_MERT_MMIO_TRG

Drive-by comment: These patches aren't really changing RTP processing or
infrastructure.  Maybe using "drm/xe/oa" as subject prefix would be more
appropriate?

--
Gustavo Sousa

>
>  drivers/gpu/drm/xe/xe_reg_whitelist.c | 12 ++++--------
>  1 file changed, 4 insertions(+), 8 deletions(-)
>
> -- 
> 2.48.1

  parent reply	other threads:[~2026-04-14 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  3:52 [PATCH 0/3] drm/xe/rtp: OA register whitelist fixes Ashutosh Dixit
2026-04-14  3:52 ` [PATCH 1/3] drm/xe/rtp: Don't whitelist OA status registers Ashutosh Dixit
2026-04-14  3:52 ` [PATCH 2/3] drm/xe/rtp: Don't whitelist OA head pointer registers Ashutosh Dixit
2026-04-14  3:52 ` [PATCH 3/3] drm/xe/rtp: Fix offset alignment for MERT WHITELIST_OA_MERT_MMIO_TRG Ashutosh Dixit
2026-04-14  4:00 ` ✗ CI.checkpatch: warning for drm/xe/rtp: OA register whitelist fixes Patchwork
2026-04-14  4:01 ` ✓ CI.KUnit: success " Patchwork
2026-04-14  5:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14  8:04 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-14 15:28 ` Gustavo Sousa [this message]
2026-04-15  3:38   ` [PATCH 0/3] " Dixit, Ashutosh

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=87se8xwoho.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox