From: Archit Taneja <archit@ti.com>
To: tomi.valkeinen@ti.com, robdclark@gmail.com
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH 0/6] drm/omap: Misc fixes
Date: Fri, 11 Apr 2014 12:53:29 +0530 [thread overview]
Message-ID: <1397201015-2807-1-git-send-email-archit@ti.com> (raw)
These are based over Tomi's 3.15/omapdrm-fixes branch.
Archit Taneja (5):
drm/omap: gem sync: wait on correct events
drm/omap: Fix crash when using LCD3 overlay manager
drm/omap: Allow allocation of larger buffers
drm/omap: Use old_fb to synchronize between successive page flips
drm/omap: protect omap_crtc's event with event_lock spinlock
Subhajit Paul (1):
drm/omap: Fix memory leak in omap_gem_op_async
drivers/gpu/drm/omapdrm/omap_crtc.c | 7 ++++++-
drivers/gpu/drm/omapdrm/omap_drv.c | 10 ++++++----
drivers/gpu/drm/omapdrm/omap_gem.c | 6 ++++--
drivers/video/omap2/dss/dispc.c | 12 ++++++++++++
include/video/omapdss.h | 2 ++
5 files changed, 30 insertions(+), 7 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-04-11 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 7:23 Archit Taneja [this message]
2014-04-11 7:23 ` [PATCH 1/6] drm/omap: Fix memory leak in omap_gem_op_async Archit Taneja
2014-04-11 7:23 ` [PATCH 2/6] drm/omap: gem sync: wait on correct events Archit Taneja
2014-04-11 7:23 ` [PATCH 3/6] drm/omap: Fix crash when using LCD3 overlay manager Archit Taneja
2014-04-11 7:23 ` [PATCH 4/6] drm/omap: Allow allocation of larger buffers Archit Taneja
2014-04-14 9:25 ` Tomi Valkeinen
2014-04-14 10:18 ` Archit Taneja
2014-04-14 10:30 ` Tomi Valkeinen
2014-04-14 11:07 ` Archit Taneja
2014-04-14 10:43 ` Rob Clark
2014-04-11 7:23 ` [PATCH 5/6] drm/omap: Use old_fb to synchronize between successive page flips Archit Taneja
2014-04-11 7:23 ` [PATCH 6/6] drm/omap: protect omap_crtc's event with event_lock spinlock Archit Taneja
2014-04-14 12:36 ` Tomi Valkeinen
2014-04-16 7:06 ` Archit Taneja
2014-04-15 9:42 ` [PATCH 0/6] drm/omap: Misc fixes Tomi Valkeinen
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=1397201015-2807-1-git-send-email-archit@ti.com \
--to=archit@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.com \
--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 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.