From: Gustavo Sousa <gustavo.sousa@intel.com>
To: "Bhadane, Dnyaneshwar" <dnyaneshwar.bhadane@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH] drm/xe/pat: Extract gt_pta_entry()
Date: Wed, 11 Mar 2026 15:48:52 -0300 [thread overview]
Message-ID: <87ms0e5hij.fsf@intel.com> (raw)
In-Reply-To: <IA1PR11MB62666C3DB0B6AE14CBBEB0A2E27CA@IA1PR11MB6266.namprd11.prod.outlook.com>
"Bhadane, Dnyaneshwar" <dnyaneshwar.bhadane@intel.com> writes:
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Gustavo
>> Sousa
>> Sent: Wednesday, March 4, 2026 2:16 AM
>> To: intel-xe@lists.freedesktop.org
>> Cc: Sousa, Gustavo <gustavo.sousa@intel.com>
>> Subject: [PATCH] drm/xe/pat: Extract gt_pta_entry()
>>
>> Avoid code duplication by extracting the logic for selection of the correct
>> PAT_PTA entry for a GT into function gt_pta_entry() and using that function
>> whenever necessary.
>>
>> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
>
> Looks good to me,
> Reviewed-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Pushed to drm-xe-next. Thanks for the review!
--
Gustavo Sousa
next prev parent reply other threads:[~2026-03-11 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 20:46 [PATCH] drm/xe/pat: Extract gt_pta_entry() Gustavo Sousa
2026-03-03 21:10 ` ✓ CI.KUnit: success for " Patchwork
2026-03-03 22:04 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-04 8:49 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-04 8:55 ` [PATCH] " Bhadane, Dnyaneshwar
2026-03-11 18:48 ` Gustavo Sousa [this message]
2026-03-05 9:45 ` ✗ Xe.CI.BAT: failure for " Patchwork
2026-03-06 7:58 ` ✓ CI.KUnit: success for drm/xe/pat: Extract gt_pta_entry() (rev2) Patchwork
2026-03-06 8:59 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-11 15:14 ` Gustavo Sousa
2026-03-07 8:30 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-11 18:01 ` Gustavo Sousa
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=87ms0e5hij.fsf@intel.com \
--to=gustavo.sousa@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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.