All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/atomic-helper: Check encoder/crtc constraints
Date: Thu, 19 Nov 2015 08:50:35 +0000	[thread overview]
Message-ID: <CAPj87rPk9dkdEFW6y4zMRsNLaLyJ+6ZRHvY9MGu_npKSWE640g@mail.gmail.com> (raw)
In-Reply-To: <1447868808-10266-1-git-send-email-daniel.vetter@ffwll.ch>

Hi,

On 18 November 2015 at 17:46, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> This was totally lost when I originally created the atomic helpers.
>
> We probably should also check possible_clones in the helpers, but
> since the legacy ones didn't do that this is for a separate patch.

Heh, before reading this chunk of the commit message, I also went
looking for possible_clones and came to the same conclusion. On the
grounds that great minds think alike (or fools never differ, not
sure):
Reviewed-by: Daniel Stone <daniels@collabora.com>

Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-11-19  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 17:46 [PATCH] drm/atomic-helper: Check encoder/crtc constraints Daniel Vetter
2015-11-19  8:50 ` Daniel Stone [this message]
2015-11-19 10:12 ` Ville Syrjälä
2015-11-19 14:02   ` Daniel Vetter
2015-11-19 14:24     ` Ville Syrjälä
2015-11-19 14:44       ` Daniel Vetter
2015-11-19 15:38 ` 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=CAPj87rPk9dkdEFW6y4zMRsNLaLyJ+6ZRHvY9MGu_npKSWE640g@mail.gmail.com \
    --to=daniel@fooishbar.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 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.