From: Jani Nikula <jani.nikula@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/3] drm/i915: nuke i915->gt0
Date: Wed, 04 Oct 2023 18:33:23 +0300 [thread overview]
Message-ID: <87il7me724.fsf@intel.com> (raw)
In-Reply-To: <ZRrOA6v1katsED65@ashyti-mobl2.lan>
On Mon, 02 Oct 2023, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> Hi Jani,
>
> adding a few folks in Cc for some extra eyes on this series.
Thanks for the reviews and acks, pushed to drm-intel-next.
drm-intel-next instead of drm-intel-gt-next because of the changes in
i915_drv.h, and it's easier to sync from din to dign than vice versa.
BR,
Jani.
>
> On Mon, Oct 02, 2023 at 11:47:01AM +0300, Jani Nikula wrote:
>> Chopping up [1] to more digestable pieces. Start off with nuking
>> i915->gt0.
>>
>> [1] https://patchwork.freedesktop.org/series/124418/
>>
>> Jani Nikula (3):
>> drm/i915/mocs: use to_gt() instead of direct &i915->gt
>> drm/i915: allocate i915->gt0 dynamically
>> drm/i915/gt: remove i915->gt0 in favour of i915->gt[0]
>>
>> drivers/gpu/drm/i915/gt/intel_gt.c | 10 +++++++---
>> drivers/gpu/drm/i915/gt/intel_mocs.c | 4 ++--
>> drivers/gpu/drm/i915/i915_drv.h | 10 ++--------
>> drivers/gpu/drm/i915/selftests/mock_gem_device.c | 1 -
>> 4 files changed, 11 insertions(+), 14 deletions(-)
>
> Michal, Michal and Tomasz, can you please check here?
>
> Thanks,
> Andi
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-04 15:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 8:47 [Intel-gfx] [PATCH 0/3] drm/i915: nuke i915->gt0 Jani Nikula
2023-10-02 8:47 ` [Intel-gfx] [PATCH 1/3] drm/i915/mocs: use to_gt() instead of direct &i915->gt Jani Nikula
2023-10-02 14:10 ` Gustavo Sousa
2023-10-03 6:26 ` Andi Shyti
2023-10-02 8:47 ` [Intel-gfx] [PATCH 2/3] drm/i915: allocate i915->gt0 dynamically Jani Nikula
2023-10-02 14:20 ` Gustavo Sousa
2023-10-03 6:54 ` Andi Shyti
2023-10-02 8:47 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: remove i915->gt0 in favour of i915->gt[0] Jani Nikula
2023-10-02 14:33 ` Gustavo Sousa
2023-10-03 7:47 ` Andi Shyti
2023-10-02 14:04 ` [Intel-gfx] [PATCH 0/3] drm/i915: nuke i915->gt0 Andi Shyti
2023-10-02 14:40 ` Andi Shyti
2023-10-02 17:18 ` Michał Winiarski
2023-10-04 15:33 ` Jani Nikula [this message]
2023-10-02 19:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-10-02 19:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-03 10:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: nuke i915->gt0 (rev2) Patchwork
2023-10-03 11:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-03 13:18 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-04 10:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: nuke i915->gt0 (rev3) Patchwork
2023-10-04 10:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-04 13:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87il7me724.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@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.