From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/2] drm/i915: use ref_tracker library in i915
Date: Tue, 31 Oct 2023 17:05:17 +0100 [thread overview]
Message-ID: <ZUElvf5qzDMqqpZp@ashyti-mobl2.lan> (raw)
In-Reply-To: <20231030-ref_tracker_i915-v1-0-006fe6b96421@intel.com>
> This patchset replaces custom tracking solution
> with ref_tracker library. This is follow-up of the
> work from patchset[1]. Core part is already merged
> and present in drm-tip. This is actually re-base of [1]
> with minor fixes for code introduced later.
>
> [1]: https://lore.kernel.org/r/20230224-track_gt-v8-0-4b6517e61be6@intel.com
>
> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
yaay!!! Finally! :-)
next prev parent reply other threads:[~2023-10-31 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 17:40 [Intel-gfx] [PATCH 0/2] drm/i915: use ref_tracker library in i915 Andrzej Hajda
2023-10-30 17:40 ` [Intel-gfx] [PATCH 1/2] drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library Andrzej Hajda
2023-10-30 17:40 ` [Intel-gfx] [PATCH 2/2] drm/i915: Track gt pm wakerefs Andrzej Hajda
2023-10-31 0:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library in i915 Patchwork
2023-10-31 0:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-31 0:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-31 16:05 ` Andi Shyti [this message]
2023-10-31 22:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library in i915 (rev2) Patchwork
2023-10-31 22:15 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-31 22:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-02 10:55 ` [Intel-gfx] â " Andrzej Hajda
2023-11-03 3:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library in i915 (rev3) Patchwork
2023-11-03 3:24 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-03 3:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-03 21:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-17 8:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library in i915 (rev4) Patchwork
2023-11-17 8:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-17 9:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-18 3:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-11-20 12:21 ` [Intel-gfx] â " Andrzej Hajda
2024-01-05 11:49 ` Jani Nikula
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=ZUElvf5qzDMqqpZp@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@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