From: Sasha Levin <sashal@kernel.org>
To: "Sasha Levin" <sashal@kernel.org>,
"Ville Syrjala" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Blubberbub@protonmail.com, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] drm/i915: Don't clobber M/N values during fastset check
Date: Sat, 15 Jun 2019 22:16:10 +0000 [thread overview]
Message-ID: <20190615221610.DADC221851@mail.kernel.org> (raw)
In-Reply-To: <20190612172423.25231-1-ville.syrjala@linux.intel.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d19f958db23c drm/i915: Enable fastset for non-boot modesets..
The bot has tested the following trees: v5.1.9.
v5.1.9: Failed to apply! Possible dependencies:
1b9994c78977 ("drm/i915: Don't pass the crtc to intel_dump_pipe_config()")
48d9f87ddd21 ("drm/i915: Save the old CDCLK atomic state")
5643dd9c7af4 ("drm/i915: Use intel_ types in intel_modeset_checks()")
59f9e9cab3a1 ("drm/i915: Skip modeset for cdclk changes if possible")
85829eb5ee1a ("drm/i915: Pass intel_atomic state to check_digital_port_conflicts()")
905801fe7237 ("drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled")
9a86a07c7e94 ("drm/i915: Use intel_ types in intel_atomic_check()")
d31c85fc8642 ("snd/hda, drm/i915: Track the display_power_status using a cookie")
f239b7998507 ("drm/i915: Don't pass the crtc to intel_modeset_pipe_config()")
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
next prev parent reply other threads:[~2019-06-15 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 13:07 [PATCH 1/4] drm/i915: Don't clobber M/N values during fastset check Ville Syrjala
2019-06-12 13:07 ` [PATCH 2/4] drm/i915: Constify intel_pipe_config_compare() Ville Syrjala
2019-06-18 12:25 ` Imre Deak
2019-06-12 13:08 ` [PATCH 3/4] drm/i915: Make pipe_config_err() vs. fastset less confusing Ville Syrjala
2019-06-12 15:43 ` Imre Deak
2019-06-12 13:08 ` [PATCH 4/4] drm/i915: Drop the _INCOMPLETE for has_infoframe Ville Syrjala
2019-06-18 12:34 ` Imre Deak
2019-06-18 12:55 ` Ville Syrjälä
2019-06-18 13:28 ` Imre Deak
2019-06-12 13:15 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Don't clobber M/N values during fastset check Patchwork
2019-06-12 13:52 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-12 17:24 ` [PATCH v2 1/4] " Ville Syrjala
2019-06-13 9:24 ` Ville Syrjälä
2019-06-18 12:19 ` [Intel-gfx] " Imre Deak
2019-06-15 22:16 ` Sasha Levin [this message]
2019-06-12 18:35 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/4] drm/i915: Don't clobber M/N values during fastset check (rev2) Patchwork
2019-06-12 19:06 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-14 13:14 ` ✓ Fi.CI.IGT: " Patchwork
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=20190615221610.DADC221851@mail.kernel.org \
--to=sashal@kernel.org \
--cc=Blubberbub@protonmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.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