All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	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 20:38:57 -0700	[thread overview]
Message-ID: <871pgg99ke.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87se8xwoho.fsf@intel.com>

On Tue, 14 Apr 2026 08:28:03 -0700, Gustavo Sousa wrote:
>
> 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?

OK, I posted a new series with "drm/xe/oa" here:

https://patchwork.freedesktop.org/series/164897/

Thanks.
--
Ashutosh

      reply	other threads:[~2026-04-15  3:39 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 ` [PATCH 0/3] " Gustavo Sousa
2026-04-15  3:38   ` Dixit, Ashutosh [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=871pgg99ke.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=gustavo.sousa@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 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.