From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
Shekhar Chauhan <shekhar.chauhan@intel.com>,
igt-dev@lists.freedesktop.org
Cc: shekhar.chauhan@intel.com, ashutosh.dixit@intel.com
Subject: Re: [PATCH v4 1/2] lib/intel_wa: Add workaround check for a wa within debugfs file
Date: Tue, 05 May 2026 17:53:14 +0300 [thread overview]
Message-ID: <7ee1d51da8b2306d5646e65a6b2bdd3f71a5173b@intel.com> (raw)
In-Reply-To: <87qznpykom.fsf@intel.com>
On Tue, 05 May 2026, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Jani Nikula <jani.nikula@intel.com> writes:
>
>> On Tue, 05 May 2026, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
>>> I think there is room for improvement on how those functions are
>>> implemented: the use of strstr() is not very robust, since it can return
>>> partial matches; and this function is currently xe-specific (i.e. can't
>>> be used for i915), so we need some assert to make sure that it is being
>>> called only for xe. However, those are unrelated to this patch and
>>> could be fixed as a follow-up change.
>>
>> There are already lib/i915 and lib/xe directories. lib/i915 and lib/
>> have a number of things that are specific to Intel (either i915 or
>> xe). lib/ has a number of things that are specific to either i915 or xe,
>> but not both.
>>
>> There's a lot of room for moving things about to improve clarity here.
>
> Yeah... Should we reorganize stuff into 3 separate directories then?
>
> - lib/intel for things common to both drivers;
> - lib/i915 for things specific to i915;
> - lib/xe for things specific to xe.
That's what I thought I was suggesting, but I realize now I didn't
really write that. ;D
BR,
Jani.
>
> --
> Gustavo Sousa
>
>>
>> BRm,
>> Jani.
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-05 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 5:47 [PATCH v4 0/2] Wa_14026633728 Shekhar Chauhan
2026-05-05 5:47 ` [PATCH v4 1/2] lib/intel_wa: Add workaround check for a wa within debugfs file Shekhar Chauhan
2026-05-05 13:34 ` Gustavo Sousa
2026-05-05 14:26 ` Jani Nikula
2026-05-05 14:50 ` Gustavo Sousa
2026-05-05 14:53 ` Jani Nikula [this message]
2026-05-05 5:47 ` [PATCH v4 2/2] tests/intel/xe_oa: Wa_14026633728 Shekhar Chauhan
2026-05-05 16:42 ` Dixit, Ashutosh
2026-05-05 6:59 ` ✓ i915.CI.BAT: success for Wa_14026633728 Patchwork
2026-05-05 7:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-05 11:50 ` ✓ i915.CI.Full: " Patchwork
2026-05-05 14:43 ` ✗ Xe.CI.FULL: failure " 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=7ee1d51da8b2306d5646e65a6b2bdd3f71a5173b@intel.com \
--to=jani.nikula@intel.com \
--cc=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