From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>
Subject: Re: [Intel-gfx] â Fi.CI.IGT: success for drm/i915: use ref_tracker library in i915 (rev4)
Date: Fri, 05 Jan 2024 13:49:07 +0200 [thread overview]
Message-ID: <87v888xaoc.fsf@intel.com> (raw)
In-Reply-To: <0a187141-2b6b-46e2-9b00-6b7b0ad9edfe@intel.com>
On Mon, 20 Nov 2023, Andrzej Hajda <andrzej.hajda@intel.com> wrote:
> Patchset merged to intel-gt-next.
For future reference, anything that has an impact outside of the gt/gem
land should be merged via drm-intel-next, not drm-intel-gt-next.
We can cross-merge drm-intel-next -> drm-intel-gt-next, but any changes
from drm-intel-gt-next back to drm-intel-next need to go via drm-next
and backmerge to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-01-05 11:49 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 ` [Intel-gfx] [PATCH 0/2] " Andi Shyti
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 [this message]
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=87v888xaoc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.org \
/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