Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Shekhar Chauhan <shekhar.chauhan@intel.com>
Cc: <igt-dev@lists.freedesktop.org>, <gustavo.sousa@intel.com>
Subject: Re: [PATCH v5 1/2] lib/intel_wa: Check for device workarounds
Date: Tue, 05 May 2026 21:25:15 -0700	[thread overview]
Message-ID: <87fr45go5w.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20260506024443.612636-2-shekhar.chauhan@intel.com>

On Tue, 05 May 2026 19:44:42 -0700, Shekhar Chauhan wrote:
>
> Currently, igt_has_intel_wa() only checks for GT workarounds, extending
> it to ensure that it also checks for device workarounds to avoid having
> device workaround checks in the code.
> While at it, ensure that we do not duplicate the logic for reading from
> the debugfs file by extracting it into a separate function called
> debugfs_file_has_wa().
>
> Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>

You need to get the patches from Patchwork first, and then work on them,
and then send them, to pick up previous R-b's (in this case Gustavo's).

  reply	other threads:[~2026-05-06  4:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  2:44 [PATCH v5 0/2] Wa_14026633728 Shekhar Chauhan
2026-05-06  2:44 ` [PATCH v5 1/2] lib/intel_wa: Check for device workarounds Shekhar Chauhan
2026-05-06  4:25   ` Dixit, Ashutosh [this message]
2026-05-06  2:44 ` [PATCH v5 2/2] tests/intel/xe_oa: Wa_14026633728 Shekhar Chauhan
2026-05-06  2:55   ` Shekhar Chauhan
2026-05-06  4:58     ` Dixit, Ashutosh
2026-05-06  6:27       ` Dixit, Ashutosh
2026-05-06  3:27 ` ✓ Xe.CI.BAT: success for Wa_14026633728 (rev2) Patchwork
2026-05-06  3:33 ` ✗ i915.CI.BAT: failure " Patchwork
2026-05-06  7:07 ` ✗ Xe.CI.FULL: " 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=87fr45go5w.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=shekhar.chauhan@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