From: Jyri Sarha <jsarha@ti.com>
To: Gustavo Padovan <gustavo@padovan.org>,
dri-devel@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
David Airlie <airlied@linux.ie>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Darren Etheridge <detheridge@ti.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 11/14] drm/tilcdc: use drm_crtc_send_vblank_event()
Date: Mon, 2 May 2016 21:58:06 +0300 [thread overview]
Message-ID: <5727A33E.8010404@ti.com> (raw)
In-Reply-To: <20160502150542.GT14148@phenom.ffwll.local>
On 05/02/16 18:05, Daniel Vetter wrote:
> On Tue, Apr 19, 2016 at 11:03:26AM -0300, Gustavo Padovan wrote:
>> Hi Jyri,
>>
>> 2016-04-19 Jyri Sarha <jsarha@ti.com>:
>>
>>> On 04/14/16 20:48, Gustavo Padovan wrote:
>>>> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>>>>
>>>> Replace the legacy drm_send_vblank_event() with the new helper function.
>>>>
>>>> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>>>
>>> Reviewed-by: Jyri Sarha <jsarha@ti.com>
>>> Tested-by: Jyri Sarha <jsarha@ti.com>
>>>
>>> Thanks!
>>> Do you prefer me to pick this one to my next pull request?
>>
>> Yes, please pick it.
>
> I didn't see a confirmation, so smashed it into drm-misc.
>
> Thanks, Daniel
>
Ok, thanks. My tilcdc atomic modeset patches are kind stalled and
without them I do not have too anything else put in the a pull req
anyway. I'll drop the patch from my branch.
BR,
Jyri
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-02 18:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:48 [PATCH 01/14] drm/amdgpu: use drm_crtc_send_vblank_event() Gustavo Padovan
2016-04-14 17:48 ` [PATCH 02/14] drm/armada: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 03/14] drm/atmel: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 04/14] drm/i915: " Gustavo Padovan
2016-04-15 7:42 ` Daniel Vetter
2016-04-14 17:48 ` [PATCH 05/14] drm/msm: " Gustavo Padovan
2016-04-14 20:51 ` Rob Clark
2016-04-19 14:02 ` Gustavo Padovan
2016-04-20 11:13 ` Daniel Vetter
2016-05-02 15:04 ` Daniel Vetter
2016-04-14 17:48 ` [PATCH 06/14] drm/qxl: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 07/14] drm/nouveau: " Gustavo Padovan
2016-04-25 7:01 ` Mario Kleiner
2016-04-25 20:06 ` Gustavo Padovan
2016-04-14 17:48 ` [PATCH 08/14] drm/radeon: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 09/14] drm/rcar-du: " Gustavo Padovan
2016-04-14 21:59 ` Laurent Pinchart
2016-04-14 17:48 ` [PATCH 10/14] drm/shmobile: " Gustavo Padovan
2016-04-14 21:59 ` Laurent Pinchart
2016-05-02 15:06 ` Daniel Vetter
2016-04-14 17:48 ` [PATCH 11/14] drm/tilcdc: " Gustavo Padovan
2016-04-19 12:56 ` Jyri Sarha
2016-04-19 14:03 ` Gustavo Padovan
2016-05-02 15:05 ` Daniel Vetter
2016-05-02 18:58 ` Jyri Sarha [this message]
2016-04-14 17:48 ` [PATCH 12/14] drm/udl: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 13/14] drm/virtio: " Gustavo Padovan
2016-04-14 17:48 ` [PATCH 14/14] drm: remove legacy drm_send_vblank_event() Gustavo Padovan
2016-04-15 2:55 ` [PATCH 01/14] drm/amdgpu: use drm_crtc_send_vblank_event() Michel Dänzer
2016-05-02 15:03 ` Daniel Vetter
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=5727A33E.8010404@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=detheridge@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).