All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/9] drm/i915: Make user contexts bannable again!
Date: Fri, 22 Feb 2019 15:24:26 +0000	[thread overview]
Message-ID: <20190222152427.E6B442070D@mail.kernel.org> (raw)
In-Reply-To: <20190217161159.815-1-chris@chris-wilson.co.uk>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 6095868a271d drm/i915: Complete kerneldoc for struct i915_gem_context.

The bot has tested the following trees: v4.20.11, v4.19.24, v4.14.102.

v4.20.11: Failed to apply! Possible dependencies:
    7651a4452ddf ("drm/i915: Reserve some priority bits for internal use")

v4.19.24: Failed to apply! Possible dependencies:
    7651a4452ddf ("drm/i915: Reserve some priority bits for internal use")

v4.14.102: Failed to apply! Possible dependencies:
    0a53bc07f044 ("drm/i915/gvt: Separate cmd scan from request allocation")
    0cce2823ed37 ("drm/i915/gvt: Refine error handling for prepare_execlist_workload")
    1406a14b0ed9 ("drm/i915/gvt: Introduce intel_vgpu_submission")
    1603660b3342 ("drm/i915/gvt: set max priority for gvt context")
    465c403cb508 ("drm/i915: introduce simple gemfs")
    54cff6479fd8 ("drm/i915/gvt: Make elsp_dwords in the right order")
    7651a4452ddf ("drm/i915: Reserve some priority bits for internal use")
    9a9829e9eb8b ("drm/i915/gvt: Move workload cache init/clean into intel_vgpu_{setup, clean}_submission()")
    a3cfdca920b2 ("drm/i915/gvt: Add error handling for intel_gvt_scan_and_shadow_workload")
    b7268c5eed0a ("drm/i915: Pack params to engine->schedule() into a struct")
    d8235b5e5584 ("drm/i915/gvt: Move common workload preparation into prepare_workload()")
    e61e0f51ba79 ("drm/i915: Rename drm_i915_gem_request to i915_request")
    e91ef99b9543 ("drm/i915/selftests: Remember to create the fake preempt context")
    f2880e04f3a5 ("drm/i915/gvt: Move request alloc to dispatch_workload path only")


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

      parent reply	other threads:[~2019-02-22 15:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 16:11 [PATCH 1/9] drm/i915: Make user contexts bannable again! Chris Wilson
2019-02-17 16:11 ` [PATCH 2/9] drm/i915: Prevent user context creation while wedged Chris Wilson
2019-02-17 16:11 ` [PATCH 3/9] drm/i915: Optionally disable automatic recovery after a GPU reset Chris Wilson
2019-02-17 17:05   ` [PATCH] " Chris Wilson
2019-02-17 16:11 ` [PATCH 4/9] drm/i915/selftests: Move local mock_ggtt allocations to the heap Chris Wilson
2019-02-17 18:40   ` Matthew Auld
2019-02-17 20:22     ` Chris Wilson
2019-02-17 16:11 ` [PATCH 5/9] drm/i915: Move verify_wm_state() to heap Chris Wilson
2019-02-17 16:11 ` [PATCH 6/9] drm/i915: Avoid reset lock in writing fence registers Chris Wilson
2019-02-17 16:11 ` [PATCH 7/9] drm/i915: Reorder struct_mutex-vs-reset_lock in i915_gem_fault() Chris Wilson
2019-02-17 16:11 ` [PATCH 8/9] drm/i915: Trim i915_do_reset() to minimum delays Chris Wilson
2019-02-17 16:11 ` [PATCH 9/9] drm/i915: Trim delays for wedging Chris Wilson
2019-02-17 16:36 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915: Make user contexts bannable again! Patchwork
2019-02-17 16:39 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-17 17:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-17 17:31 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915: Make user contexts bannable again! (rev2) Patchwork
2019-02-17 17:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-17 17:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-17 23:12 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-02-18 10:45 ` [PATCH 1/9] drm/i915: Make user contexts bannable again! Mika Kuoppala
2019-02-18 10:45   ` Mika Kuoppala
2019-02-18 10:51   ` Chris Wilson
2019-02-22 15:24 ` Sasha Levin [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=20190222152427.E6B442070D@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --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.