From: Lucas Stach <l.stach@pengutronix.de>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org,
etnaviv@lists.freedesktop.org
Subject: [GIT PULL] etnaviv-next for 5.1
Date: Thu, 28 Feb 2019 07:05:32 +0100 [thread overview]
Message-ID: <4bc1a4c8447bb947d2fe8facd0ff09c5b8753087.camel@pengutronix.de> (raw)
Hi Daniel, hi Dave,
sorry for being really late. We don't have something major to destage,
as per-process address spaces and softpin are still baking. So this
time around it's only small fixes and a change to not restrict etnaviv
to certain architectures. This has seen some coverage from the kbuild
bot and has also been in linux-next for a few weeks already.
Regards,
Lucas
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
https://git.pengutronix.de/git/lst/linux etnaviv/next
for you to fetch changes up to 9e05352340d3a3e68c144136db9810b26ebb88c3:
drm/etnaviv: potential NULL dereference (2019-02-11 11:50:43 +0100)
----------------------------------------------------------------
Dan Carpenter (3):
drm/etnaviv: fix some off by one bugs
drm/etnaviv: NULL vs IS_ERR() buf in etnaviv_core_dump()
drm/etnaviv: potential NULL dereference
Lucas Stach (3):
drm/etnaviv: move job context pointer to etnaviv_gem_submit
drm/etnaviv: don't restrict to certain architectures
drm/etnaviv: mmuv2: don't map zero page
Matthew Wilcox (2):
etnaviv mailing list is moderated
Build etnaviv on non-ARM architectures
MAINTAINERS | 2 +-
drivers/gpu/drm/etnaviv/Kconfig | 1 -
drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.h | 2 --
drivers/gpu/drm/etnaviv/etnaviv_dump.c | 2 +-
drivers/gpu/drm/etnaviv/etnaviv_gem.h | 1 +
drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c | 2 +-
drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 2 +-
drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c | 4 ++--
drivers/gpu/drm/etnaviv/etnaviv_perfmon.c | 6 +++---
drivers/gpu/drm/etnaviv/etnaviv_sched.c | 2 +-
10 files changed, 11 insertions(+), 13 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2019-02-28 6:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4bc1a4c8447bb947d2fe8facd0ff09c5b8753087.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
/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.