From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Joseph Yasi <joe.yasi@gmail.com>
Subject: Re: [v4.3/-fixes PATCH/BACKPORT 0/4] plane related backports to -fixes
Date: Wed, 14 Oct 2015 11:06:24 +0200 [thread overview]
Message-ID: <561E1B10.3040502@linux.intel.com> (raw)
In-Reply-To: <cover.1444813465.git.jani.nikula@intel.com>
Op 14-10-15 om 11:06 schreef Jani Nikula:
> I'm proposing to backport these to v4.3/-fixes, objections or acks?
>
> BR,
> Jani.
>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=91910#c4
>
>
> Jani Nikula (1):
> Revert "drm/i915: Add primary plane to mask if it's visible"
>
> Maarten Lankhorst (1):
> drm/i915: Add primary plane to mask if it's visible
>
> Ville Syrjälä (2):
> drm/i915: Assign hwmode after encoder state readout
> drm/i915: Move sprite/cursor plane disable to intel_sanitize_crtc()
>
> drivers/gpu/drm/i915/intel_display.c | 106 +++++++++++++++++------------------
> 1 file changed, 53 insertions(+), 53 deletions(-)
>
Acking all.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-14 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 9:06 [v4.3/-fixes PATCH/BACKPORT 0/4] plane related backports to -fixes Jani Nikula
2015-10-14 9:06 ` Maarten Lankhorst [this message]
2015-10-14 12:19 ` Jani Nikula
2015-10-14 9:06 ` [v4.3/-fixes PATCH/BACKPORT 1/4] Revert "drm/i915: Add primary plane to mask if it's visible" Jani Nikula
2015-10-14 9:06 ` [v4.3/-fixes PATCH/BACKPORT 2/4] drm/i915: Assign hwmode after encoder state readout Jani Nikula
2015-10-14 9:06 ` [v4.3/-fixes PATCH/BACKPORT 3/4] drm/i915: Move sprite/cursor plane disable to intel_sanitize_crtc() Jani Nikula
2015-10-14 9:06 ` [v4.3/-fixes PATCH/BACKPORT 4/4] drm/i915: Add primary plane to mask if it's visible Jani Nikula
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=561E1B10.3040502@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=joe.yasi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox