From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH v8 1/2] drm/i915: preparation for using PAT index
Date: Tue, 27 Jun 2023 18:16:37 +0300 [thread overview]
Message-ID: <871qhxszoq.fsf@intel.com> (raw)
In-Reply-To: <ZJr6aRb8SrLug7SQ@ashyti-mobl2.lan>
On Tue, 27 Jun 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> Tvrtko wrote:
>> I'd simply suggest having a local static const table for the mock device. It
>> should be trivial once i915->__info becomes a pointer so in that series I
>> guess.
That's a great idea, thanks!
> Fei... do you have bandwidth to look into this or do you want me
> to try Tvrtko's suggestion out?
https://patchwork.freedesktop.org/patch/msgid/b0db62045a96a3fd4cf123685da88cc777f9b485.1687878757.git.jani.nikula@intel.com
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-06-27 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 16:51 [Intel-gfx] [PATCH v8 0/2] drm/i915: use pat_index instead of cache_level fei.yang
2023-05-09 16:51 ` [Intel-gfx] [PATCH v8 1/2] drm/i915: preparation for using PAT index fei.yang
2023-06-27 13:28 ` Jani Nikula
2023-06-27 14:05 ` Tvrtko Ursulin
2023-06-27 15:04 ` Andi Shyti
2023-06-27 15:16 ` Jani Nikula [this message]
2023-06-27 15:19 ` Yang, Fei
2023-06-27 15:36 ` Yang, Fei
2023-05-09 16:52 ` [Intel-gfx] [PATCH v8 2/2] drm/i915: use pat_index instead of cache_level fei.yang
2023-05-09 17:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-05-09 18:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-09 19:42 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-11 15:59 ` [Intel-gfx] [PATCH v8 0/2] " Andi Shyti
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=871qhxszoq.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=tvrtko.ursulin@linux.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