All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Sharma, Nishit" <nishit.sharma@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Girotra, Himanshu" <himanshu.girotra@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [PATCH i-g-t] Revert "lib/intel_pat: use kernel debugfs as authoritative PAT source for Xe"
Date: Wed, 04 Mar 2026 19:41:56 -0800	[thread overview]
Message-ID: <87pl5j54e3.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <MW4PR11MB71513EA99A9655ED36977DD5E47DA@MW4PR11MB7151.namprd11.prod.outlook.com>

On Wed, 04 Mar 2026 18:27:43 -0800, Sharma, Nishit wrote:
>
> Hi Ashutosh,
>
> I understand the concern but the xe_pat patch was reviewed and +1 given
> by MattR and with reasoning regarding xe_oa
> https://patchwork.freedesktop.org/patch/706754/?series=161927&rev=2
> Hence, we went ahead with the merge. In case if you feel it's major
> regression a partial revert of lib changes can be done.

Sorry, if you solve fix one area of the code, you can't break a different
area. That is the basic premise of software development. The patch should
not have been merged when you saw that you were causing regressions and
your solution was incomplete.

  reply	other threads:[~2026-03-05  3:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  0:30 [PATCH i-g-t] Revert "lib/intel_pat: use kernel debugfs as authoritative PAT source for Xe" Ashutosh Dixit
2026-03-05  2:27 ` Sharma, Nishit
2026-03-05  3:41   ` Dixit, Ashutosh [this message]
2026-03-05  4:05   ` Matt Roper
2026-03-05 12:48     ` Zbigniew Kempczyński
2026-03-05 20:15     ` Kamil Konieczny
2026-03-05 20:51       ` Matt Roper
2026-03-05 12:05 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-05 13:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-05 21:16 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-06 10:05 ` ✓ i915.CI.Full: success " Patchwork

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=87pl5j54e3.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=himanshu.girotra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=nishit.sharma@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.