All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, Lyude Paul <lyude@redhat.com>
Cc: Todd Previte <tprevite@gmail.com>,
	intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
	Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] drm/i915: Don't send MST hotplugs until after resume
Date: Tue, 29 Jan 2019 00:35:12 +0000	[thread overview]
Message-ID: <20190129003512.D365C2177E@mail.kernel.org> (raw)
In-Reply-To: <20190126012436.31382-1-lyude@redhat.com>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 0e32b39ceed6 drm/i915: add DP 1.2 MST support (v0.7).

The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153, v4.4.172, v3.18.133.

v4.20.5: Build OK!
v4.19.18: Build OK!
v4.14.96: Failed to apply! Possible dependencies:
    1a4313d13b69 ("drm/i915: Rewrite mst suspend/resume in terms of encoders")

v4.9.153: Failed to apply! Possible dependencies:
    1a4313d13b69 ("drm/i915: Rewrite mst suspend/resume in terms of encoders")

v4.4.172: Failed to apply! Possible dependencies:
    1a4313d13b69 ("drm/i915: Rewrite mst suspend/resume in terms of encoders")
    61642ff03523 ("drm/i915: Inspect subunit states on hangcheck")
    ca82580c9cea ("drm/i915: Do not call API requiring struct_mutex where it is not available")
    cbdc12a9fc9d ("drm/i915: make A0 wa's applied to A1")
    e28e404c3e93 ("drm/i915: tidy up a few leftovers")
    e2f80391478a ("drm/i915: Rename local struct intel_engine_cs variables")
    e87a005d90c3 ("drm/i915: add helpers for platform specific revision id range checks")
    ed54c1a1d11c ("drm/i915: abolish separate per-ring default_context pointers")
    ef712bb4b700 ("drm/i915: remove parens around revision ids")
    fac5e23e3c38 ("drm/i915: Mass convert dev->dev_private to to_i915(dev)")
    fffda3f4fb49 ("drm/i915/bxt: add revision id for A1 stepping and use it")

v3.18.133: Failed to apply! Possible dependencies:
    08524a9ffa39 ("drm/i915/skl: Restore pipe B/C interrupts")
    1a4313d13b69 ("drm/i915: Rewrite mst suspend/resume in terms of encoders")
    2363d8c97f87 ("drm/i915: Restore resume irq ordering comment")
    2aeb7d3a4d42 ("drm/i915: s/pm._irqs_disabled/pm.irqs_enabled/")
    2eb5252e2fff ("drm/i915: disable rps irqs earlier during suspend/unload")
    8a8b009d1337 ("drm/i915/skl: Skylake shares the interrupt logic with Broadwell")
    970104fac6ca ("drm/i915: Remove intel_modeset_suspend_hw")
    9c065a7d5b67 ("drm/i915: Extract intel_runtime_pm.c")
    b963291cf9af ("drm/i915: Use dev_priv instead of dev in irq setup functions")
    d2dee86cece9 ("drm/i915: extract intel_init_fbc()")
    fac6adb06a53 ("drm/i915: fix RPS on runtime suspend")


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-01-29  0:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  1:24 [PATCH] drm/i915: Don't send MST hotplugs until after resume Lyude Paul
2019-01-26  1:24 ` Lyude Paul
2019-01-26  2:40 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-26  7:18 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-26 23:49 ` ✓ Fi.CI.BAT: success for drm/i915: Don't send MST hotplugs until after resume (rev2) Patchwork
2019-01-27  0:42 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-28 12:44 ` [Intel-gfx] [PATCH] drm/i915: Don't send MST hotplugs until after resume Imre Deak
2019-01-29  0:35 ` Sasha Levin [this message]
2019-01-29  0:35 ` 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=20190129003512.D365C2177E@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=airlied@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tprevite@gmail.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.