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: Daniel Kamil Kozar <dkk089@gmail.com>, stable@vger.kernel.org
Subject: Re: [PATCH -fixes] drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen
Date: Thu, 07 Feb 2019 16:32:12 +0000 [thread overview]
Message-ID: <20190207163212.EB38021924@mail.kernel.org> (raw)
In-Reply-To: <20190205141846.6053-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: 516a49cc1946 drm/i915: Fix assert_plane() warning on bootup with external display.
The bot has tested the following trees: v4.20.6.
v4.20.6: Failed to apply! Possible dependencies:
c84c6fe30302 ("drm/i915: make encoder enable and disable hooks optional")
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-02-07 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 13:42 Fixes that failed to apply to v5.0-rc5 Jani Nikula
2019-02-05 14:18 ` [PATCH -fixes] drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen Ville Syrjala
2019-02-06 7:11 ` [Intel-gfx] " Jani Nikula
2019-02-07 16:32 ` Sasha Levin [this message]
2019-02-05 14:23 ` Fixes that failed to apply to v5.0-rc5 Ville Syrjälä
2019-02-06 7:13 ` Jani Nikula
2019-02-07 21:26 ` Sean Paul
2019-02-05 16:01 ` ✗ Fi.CI.BAT: failure for drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen (rev3) Patchwork
2019-02-08 13:07 ` Fixes that failed to apply to v5.0-rc5 Aditya Swarup
2019-02-08 17:51 ` Rodrigo Vivi
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=20190207163212.EB38021924@mail.kernel.org \
--to=sashal@kernel.org \
--cc=dkk089@gmail.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