All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: dri-devel <dri-devel@lists.freedesktop.org>
Cc: Sean Paul <seanpaul@chromium.org>,
	Marissa Wall <marissaw@google.com>,
	Alistair Strachan <astrachan@google.com>,
	Emil Velikov <emil.velikov@collabora.com>
Subject: [RFC][PATCH 0/5] libdrm: Patches from AOSP
Date: Fri, 19 Apr 2019 21:24:50 -0700	[thread overview]
Message-ID: <1555734295-31015-1-git-send-email-john.stultz@linaro.org> (raw)

Over the last few days I've been trying to sync the AOSP libdrm
tree with the upstream freedesktop branch.

Thanks to input from Sean, Alistair and Marissa, we've managed
to drop a bunch of stale patches AOSP was carrying, and get
the AOSP libdrm updated to 2.4.97

I've gone through the remaining patch delta and wanted to submit
the non-Android.bp changes, which seemed like they might be
relevant for upstream, for review and feedback.

With the exception of one of these, I'm not the original author,
so I do not have the full context for the patch. So if they
don't really make sense anymore, let me know and I can see if we
can drop them in AOSP.

Thoughts and feedback would be greatly appreciated!

thanks
-john

Cc: Emil Velikov <emil.velikov@collabora.com>
Cc: Sean Paul <seanpaul@chromium.org>
Cc: Alistair Strachan <astrachan@google.com>
Cc: Marissa Wall <marissaw@google.com>

Adrian Salido (1):
  libdrm: reduce number of reallocations in drmModeAtomicAddProperty

Hemant Hariyani (1):
  libdrm: omap: Add DRM_RDWR flag to dmabuf export

John Stultz (1):
  libdrm: amdgpu: Initialize unions with memset rather than "= {0}"

Prabhanjan Kandula (1):
  libdrm: Avoid additional drm open close

Sean Paul (1):
  libdrm: Use mmap64 instead of __mmap2

 amdgpu/amdgpu_cs.c | 9 ++++++---
 libdrm_macros.h    | 4 +---
 omap/omap_drm.c    | 2 +-
 xf86drm.c          | 4 ++--
 xf86drmMode.c      | 7 ++++---
 5 files changed, 14 insertions(+), 12 deletions(-)

-- 
2.7.4

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-04-20  4:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20  4:24 John Stultz [this message]
2019-04-20  4:24 ` [RFC][PATCH 1/5] libdrm: Use mmap64 instead of __mmap2 John Stultz
2019-04-22 15:03   ` Alex Deucher
2019-04-23  9:47   ` Emil Velikov
2019-04-20  4:24 ` [RFC][PATCH 2/5] libdrm: amdgpu: Initialize unions with memset rather than "= {0}" John Stultz
2019-04-22 14:58   ` Alex Deucher
2019-04-22 18:35     ` John Stultz
2019-04-23 12:51       ` Christian König
2019-04-23 10:13   ` Emil Velikov
2019-04-20  4:24 ` [RFC][PATCH 3/5] libdrm: Avoid additional drm open close John Stultz
2019-04-22 15:00   ` Alex Deucher
2019-04-20  4:24 ` [RFC][PATCH 4/5] libdrm: reduce number of reallocations in drmModeAtomicAddProperty John Stultz
2019-04-22 15:06   ` Alex Deucher
2019-04-23 10:12   ` Emil Velikov
2019-04-20  4:24 ` [RFC][PATCH 5/5] libdrm: omap: Add DRM_RDWR flag to dmabuf export John Stultz
2019-04-23 10:26   ` Emil Velikov
2019-04-23 12:56     ` Christian König

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=1555734295-31015-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=astrachan@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.velikov@collabora.com \
    --cc=marissaw@google.com \
    --cc=seanpaul@chromium.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.