From: Jani Nikula <jani.nikula@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v1 0/3] Fix modeset transitions related to DBuf
Date: Sat, 15 Feb 2020 20:27:20 +0200 [thread overview]
Message-ID: <87a75j6707.fsf@intel.com> (raw)
In-Reply-To: <20200213140412.32697-1-stanislav.lisovskiy@intel.com>
On Thu, 13 Feb 2020, Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> wrote:
> There are three existing issues, causing possible screen
> corruptions, being addressed with those patch series.
> They should go hand in hand, otherwise magic is not working.
Pushed the series, thanks for the patches, reviews and acks.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-02-15 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:04 [Intel-gfx] [PATCH v1 0/3] Fix modeset transitions related to DBuf Stanislav Lisovskiy
2020-02-13 14:04 ` [Intel-gfx] [PATCH v1 1/3] drm/i915: Ensure no conflicts with BIOS when updating Dbuf Stanislav Lisovskiy
2020-02-13 20:25 ` Matt Roper
2020-02-13 14:04 ` [Intel-gfx] [PATCH v1 2/3] drm/i915/dsc: force full modeset whenever DSC is enabled at probe Stanislav Lisovskiy
2020-02-13 20:56 ` Matt Roper
2020-02-13 21:03 ` Jani Nikula
2020-02-13 21:06 ` Matt Roper
2020-02-13 21:21 ` Jani Nikula
2020-02-13 14:04 ` [Intel-gfx] [PATCH v1 3/3] drm/i915: Force state->modeset=true when distrust_bios_wm==true Stanislav Lisovskiy
2020-02-13 21:08 ` Matt Roper
2020-02-13 16:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix modeset transitions related to DBuf Patchwork
2020-02-13 17:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-15 12:33 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-15 18:27 ` Jani Nikula [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=87a75j6707.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stanislav.lisovskiy@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