dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: Marek Vasut <marex@denx.de>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/simple-kms-helper: Plumb plane state to the enable hook
Date: Sat, 24 Mar 2018 12:26:32 -0500	[thread overview]
Message-ID: <600951bb-664e-e56a-b2de-2c2a7f4f1a74@lechnology.com> (raw)
In-Reply-To: <20180322202738.25817-1-ville.syrjala@linux.intel.com>

On 03/22/2018 03:27 PM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> We'll need access to the plane state during .atomic_enable().
> 

Some more details in the commit message would be useful. It is
not clear to me why this change is being made.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-03-24 17:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 20:27 [PATCH 1/2] drm/simple-kms-helper: Plumb plane state to the enable hook Ville Syrjala
2018-03-22 20:27 ` [PATCH 2/2] drm/tinydrm: Make fb_dirty into a lower level hook Ville Syrjala
2018-03-22 23:43   ` Noralf Trønnes
2018-03-23 11:31     ` Ville Syrjälä
2018-03-23 13:37       ` Noralf Trønnes
2018-03-23 13:58         ` Ville Syrjälä
2018-03-23 15:36           ` [Intel-gfx] " Ville Syrjälä
2018-03-23 15:35   ` [PATCH v2 " Ville Syrjala
2018-03-23 16:28     ` Noralf Trønnes
2018-03-28 16:23       ` Ville Syrjälä
2018-03-24 17:22     ` David Lechner
2018-03-24 17:26 ` David Lechner [this message]
2018-03-27 10:07   ` [PATCH 1/2] drm/simple-kms-helper: Plumb plane state to the enable hook Ville Syrjälä
2018-03-27 16:40     ` David Lechner

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=600951bb-664e-e56a-b2de-2c2a7f4f1a74@lechnology.com \
    --to=david@lechnology.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=marex@denx.de \
    --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