All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	CQ Tang <cq.tang@intel.com>,
	stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: [PATCH 1/3] drm: Restore driver.preclose() for all to use
Date: Mon, 27 Jul 2020 21:24:39 +0000	[thread overview]
Message-ID: <20200727212439.B969B2173E@mail.kernel.org> (raw)
In-Reply-To: <20200723172119.17649-1-chris@chris-wilson.co.uk>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 4.12+

The bot has tested the following trees: v5.7.10, v5.4.53, v4.19.134, v4.14.189.

v5.7.10: Build OK!
v5.4.53: Build OK!
v4.19.134: Build OK!
v4.14.189: Failed to apply! Possible dependencies:
    112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
    1572042a4ab2 ("drm: provide management functions for drm_file")
    7a2c65dd32b1 ("drm: Release filp before global lock")
    7e13ad896484 ("drm: Avoid drm_global_mutex for simple inc/dec of dev->open_count")
    b46a33e271ed ("drm/i915/pmu: Expose a PMU interface for perf queries")
    c2400ec3b6d1 ("drm/i915: add Makefile magic for testing headers are self-contained")
    cc662126b413 ("drm/i915: Introduce DRM_I915_GEM_MMAP_OFFSET")
    e7af3116836f ("drm/i915: Introduce a preempt context")
    f0e4a0639752 ("drm/i915: Move GEM domain management to its own file")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm: Restore driver.preclose() for all to use
Date: Mon, 27 Jul 2020 21:24:39 +0000	[thread overview]
Message-ID: <20200727212439.B969B2173E@mail.kernel.org> (raw)
In-Reply-To: <20200723172119.17649-1-chris@chris-wilson.co.uk>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 4.12+

The bot has tested the following trees: v5.7.10, v5.4.53, v4.19.134, v4.14.189.

v5.7.10: Build OK!
v5.4.53: Build OK!
v4.19.134: Build OK!
v4.14.189: Failed to apply! Possible dependencies:
    112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
    1572042a4ab2 ("drm: provide management functions for drm_file")
    7a2c65dd32b1 ("drm: Release filp before global lock")
    7e13ad896484 ("drm: Avoid drm_global_mutex for simple inc/dec of dev->open_count")
    b46a33e271ed ("drm/i915/pmu: Expose a PMU interface for perf queries")
    c2400ec3b6d1 ("drm/i915: add Makefile magic for testing headers are self-contained")
    cc662126b413 ("drm/i915: Introduce DRM_I915_GEM_MMAP_OFFSET")
    e7af3116836f ("drm/i915: Introduce a preempt context")
    f0e4a0639752 ("drm/i915: Move GEM domain management to its own file")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: CQ Tang <cq.tang@intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/3] drm: Restore driver.preclose() for all to use
Date: Mon, 27 Jul 2020 21:24:39 +0000	[thread overview]
Message-ID: <20200727212439.B969B2173E@mail.kernel.org> (raw)
In-Reply-To: <20200723172119.17649-1-chris@chris-wilson.co.uk>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 4.12+

The bot has tested the following trees: v5.7.10, v5.4.53, v4.19.134, v4.14.189.

v5.7.10: Build OK!
v5.4.53: Build OK!
v4.19.134: Build OK!
v4.14.189: Failed to apply! Possible dependencies:
    112ed2d31a46 ("drm/i915: Move GraphicsTechnology files under gt/")
    1572042a4ab2 ("drm: provide management functions for drm_file")
    7a2c65dd32b1 ("drm: Release filp before global lock")
    7e13ad896484 ("drm: Avoid drm_global_mutex for simple inc/dec of dev->open_count")
    b46a33e271ed ("drm/i915/pmu: Expose a PMU interface for perf queries")
    c2400ec3b6d1 ("drm/i915: add Makefile magic for testing headers are self-contained")
    cc662126b413 ("drm/i915: Introduce DRM_I915_GEM_MMAP_OFFSET")
    e7af3116836f ("drm/i915: Introduce a preempt context")
    f0e4a0639752 ("drm/i915: Move GEM domain management to its own file")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

  parent reply	other threads:[~2020-07-27 21:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 17:21 [PATCH 1/3] drm: Restore driver.preclose() for all to use Chris Wilson
2020-07-23 17:21 ` Chris Wilson
2020-07-23 17:21 ` [Intel-gfx] " Chris Wilson
2020-07-23 17:21 ` [PATCH 2/3] drm/i915/gem: Move context decoupling from postclose to preclose Chris Wilson
2020-07-23 17:21   ` Chris Wilson
2020-07-23 17:21   ` [Intel-gfx] " Chris Wilson
2020-07-23 17:44   ` Tang, CQ
2020-07-23 17:44     ` Tang, CQ
2020-07-23 17:44     ` [Intel-gfx] " Tang, CQ
2020-07-23 17:48     ` Chris Wilson
2020-07-23 17:48       ` [Intel-gfx] " Chris Wilson
2020-07-23 17:21 ` [PATCH 3/3] drm/i915/gem: Serialise debugfs i915_gem_objects with ctx->mutex Chris Wilson
2020-07-23 17:21   ` Chris Wilson
2020-07-23 17:21   ` [Intel-gfx] " Chris Wilson
2020-07-27 21:24   ` Sasha Levin
2020-07-27 21:24     ` Sasha Levin
2020-07-27 21:24     ` [Intel-gfx] " Sasha Levin
2020-09-14 16:45   ` Tvrtko Ursulin
2020-09-14 16:45     ` Tvrtko Ursulin
2020-09-14 16:45     ` Tvrtko Ursulin
2020-09-16  7:42     ` Daniel Vetter
2020-09-16  7:42       ` Daniel Vetter
2020-09-16  7:42       ` Daniel Vetter
2020-09-16  8:27       ` Tvrtko Ursulin
2020-09-16  8:27         ` Tvrtko Ursulin
2020-09-16  8:27         ` Tvrtko Ursulin
2020-07-23 17:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm: Restore driver.preclose() for all to use Patchwork
2020-07-23 17:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-07-23 17:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-23 20:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-07-27 19:32 ` [PATCH 1/3] " Daniel Vetter
2020-07-27 19:32   ` Daniel Vetter
2020-07-27 19:32   ` [Intel-gfx] " Daniel Vetter
2020-07-27 20:11   ` Tang, CQ
2020-07-27 20:11     ` Tang, CQ
2020-07-27 20:11     ` [Intel-gfx] " Tang, CQ
2020-07-28 16:27   ` Chris Wilson
2020-07-28 16:27     ` Chris Wilson
2020-07-28 16:27     ` [Intel-gfx] " Chris Wilson
2020-07-29 15:09     ` Tang, CQ
2020-07-29 15:09       ` Tang, CQ
2020-07-29 15:09       ` [Intel-gfx] " Tang, CQ
2020-07-27 21:24 ` Sasha Levin [this message]
2020-07-27 21:24   ` Sasha Levin
2020-07-27 21:24   ` [Intel-gfx] " Sasha Levin

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=20200727212439.B969B2173E@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=cq.tang@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.com \
    --cc=stable@vger.kernel.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 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.