From: Egbert Eich <e4t@freenet.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/i915: Always enable the cursor right after the primary plane
Date: Thu, 23 May 2013 13:07:56 +0200 [thread overview]
Message-ID: <20130523110756.GG14034@debian> (raw)
In-Reply-To: <20130522111528.GD28346@intel.com>
On Wed, May 22, 2013 at 02:15:28PM +0300, Ville Syrjälä wrote:
>
> I couldn't reproduce the original problem on my g4x :(
Ville, just go ahead with your patch. I will test this as soon
as I have access to a system where I know I can reproduce this.
I'll get back to you then.
>
> > Therefore:
> >
> > Acked-by: Egbert Eich <eich@suse.com>
> >
Cheers,
Egbert.
next prev parent reply other threads:[~2013-05-23 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 9:50 [PATCH 0/6] drm/i915: Unfify some modeset sequences ville.syrjala
2013-05-08 9:50 ` [PATCH 1/6] drm/i915: Always load the display palette before enabling the pipe ville.syrjala
2013-05-08 21:29 ` Jesse Barnes
2013-05-31 17:09 ` [PATCH v2] " ville.syrjala
2013-05-31 18:59 ` Daniel Vetter
2013-05-08 9:50 ` [PATCH 2/6] drm/i915: Always enable the cursor right after the primary plane ville.syrjala
2013-05-21 15:17 ` Egbert Eich
2013-05-22 11:15 ` Ville Syrjälä
2013-05-23 11:07 ` Egbert Eich [this message]
2013-06-06 16:30 ` Egbert Eich
2013-06-06 17:34 ` Ville Syrjälä
2013-05-08 9:50 ` [PATCH 3/6] drm/i915: Enable the overlay right after primary and cursor planes ville.syrjala
2013-05-08 9:50 ` [PATCH 4/6] drm/i915: Follow the same sequence when disabling planes ville.syrjala
2013-05-08 9:50 ` [PATCH 5/6] drm/i915: Drop overlay DPMS call from valleyview_crtc_enable ville.syrjala
2013-05-08 9:50 ` [PATCH 6/6] drm/i915: Disable/restore all sprite planes around modeset ville.syrjala
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=20130523110756.GG14034@debian \
--to=e4t@freenet.de \
--cc=intel-gfx@lists.freedesktop.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 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.