From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915: calculate primary visibility changes instead of calling from set_config
Date: Tue, 11 Aug 2015 13:26:27 +0200 [thread overview]
Message-ID: <55C9DBE3.6020905@linux.intel.com> (raw)
In-Reply-To: <8737zqulib.fsf@intel.com>
Op 11-08-15 om 13:12 schreef Jani Nikula:
> On Tue, 11 Aug 2015, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
>> This should be much cleaner, with the same effects.
>>
>> (cherry picked from commit fb9d6cf8c29bfcb0b3c602f7ded87f128d730382)
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> Cc: stable@vger.kernel.org #v4.2
> I don't understand. v4.2 has not been released, and we can still queue
> fixes for the release.
>
Ok in that case just queue both patches for v4.2. :)
prev parent reply other threads:[~2015-08-11 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:31 [PATCH 1/2] drm/i915: calculate primary visibility changes instead of calling from set_config Maarten Lankhorst
2015-08-11 10:31 ` [PATCH 2/2] drm/i915: Commit planes on each crtc separately Maarten Lankhorst
2015-08-12 14:46 ` Ander Conselvan De Oliveira
2015-08-13 11:53 ` Jani Nikula
2015-08-11 11:12 ` [PATCH 1/2] drm/i915: calculate primary visibility changes instead of calling from set_config Jani Nikula
2015-08-11 11:26 ` Maarten Lankhorst [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=55C9DBE3.6020905@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.kernel.org \
/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