From: Sinclair Yeh <syeh@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
dri-devel@lists.freedesktop.org,
Thomas Hellstrom <thellstrom@vmware.com>
Subject: Re: [PATCH 0/5] drm: drm_plane_helper_check_state() related stuff
Date: Mon, 20 Nov 2017 09:32:56 -0800 [thread overview]
Message-ID: <20171120173255.GA37773@promb-2n-dhcp302.eng.vmware.com> (raw)
In-Reply-To: <20171120073450.qnhq7jauakjf7blp@phenom.ffwll.local>
On Mon, Nov 20, 2017 at 08:34:50AM +0100, Daniel Vetter wrote:
> On Fri, Nov 10, 2017 at 11:42:59PM +0200, Ville Syrjälä wrote:
> > On Fri, Nov 10, 2017 at 01:26:47PM -0800, Sinclair Yeh wrote:
> > > Sorry this took so long.
> >
> > No worries.
> >
> > >
> > > The vmwgfx part: Reviewed-by: Sinclair Yeh <syeh@vmware.com>
> > >
> > > I've done some testing and the vmwgfx part looks good. Has Daniel
> > > already taken these or should I put them in my next request?
> >
> > You can take them, or I can push them to drm-misc-next. Whatever
> > works best for you.
> >
> > And I'll want to revisit this topic soonish and move the clip
> > handling into the helper as discussed with Daniel. But that can
> > wait a bit until we get this round merged somewhere.
>
> Because we're still in the merge window I think it's probably best if we
> push the entire series in through drm-misc. Tree-coordination in the merge
> window is always a bit a pain.
> -Daniel
Ok, so I'll leave this series to you then.
thanks,
Sinclair
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-20 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 18:29 [PATCH 0/5] drm: drm_plane_helper_check_state() related stuff Ville Syrjala
2017-11-01 18:29 ` [PATCH 1/5] drm/vmwgfx: Remove bogus crtc coords vs fb size check Ville Syrjala
2017-11-02 10:04 ` Daniel Vetter
2017-11-23 9:54 ` Laurent Pinchart
2017-11-01 18:29 ` [PATCH 2/5] drm/vmwgfx: Use drm_plane_helper_check_state() Ville Syrjala
2017-11-02 10:06 ` Daniel Vetter
2017-11-23 9:54 ` Laurent Pinchart
2017-11-01 18:29 ` [PATCH 3/5] drm/vmwgfx: Try to fix plane clipping Ville Syrjala
2017-11-02 10:12 ` Daniel Vetter
2017-11-02 13:19 ` Ville Syrjälä
2017-11-06 18:04 ` [Intel-gfx] " Ville Syrjälä
2017-11-07 12:30 ` Daniel Vetter
2017-11-23 9:46 ` [Intel-gfx] " Laurent Pinchart
2017-11-01 18:29 ` [PATCH 4/5] drm: Check crtc_state->enable rather than crtc->enabled in drm_plane_helper_check_state() Ville Syrjala
2017-11-01 20:15 ` [PATCH v2 " Ville Syrjala
2017-11-02 10:15 ` Daniel Vetter
2017-11-23 9:52 ` [PATCH " Laurent Pinchart
2017-11-01 18:29 ` [PATCH 5/5] drm: Move drm_plane_helper_check_state() into drm_atomic_helper.c Ville Syrjala
2017-11-01 20:16 ` [PATCH v2 " Ville Syrjala
2017-11-02 10:16 ` Daniel Vetter
2017-11-23 9:53 ` [PATCH " Laurent Pinchart
2017-11-10 21:26 ` [PATCH 0/5] drm: drm_plane_helper_check_state() related stuff Sinclair Yeh
2017-11-10 21:42 ` Ville Syrjälä
2017-11-20 7:34 ` Daniel Vetter
2017-11-20 17:32 ` Sinclair Yeh [this message]
2017-11-20 19:36 ` Ville Syrjälä
2017-11-23 9:56 ` Laurent Pinchart
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=20171120173255.GA37773@promb-2n-dhcp302.eng.vmware.com \
--to=syeh@vmware.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=thellstrom@vmware.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;
as well as URLs for NNTP newsgroup(s).