From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL] drm/tegra: Fixes for v3.13-rc3
Date: Tue, 3 Dec 2013 10:26:13 +0100 [thread overview]
Message-ID: <20131203092612.GA21178@ulmo.nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
Hi Dave,
The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
are available in the git repository at:
git://anongit.freedesktop.org/tegra/linux tags/drm/for-3.13-rc3
for you to fetch changes up to 9a991600e379641b9c16310b87ca848b6da01c24:
drm/tegra: return -EFAULT if copy_from_user() fails (2013-12-03 10:14:03 +0100)
Thanks,
Thierry
----------------------------------------------------------------
drm/tegra: Fixes for v3.13-rc3
This assortment of patches fix a few build and sparse warnings and make
sure to always return -EFAULT on copy_from_user() failures. Finally the
upcasting from struct drm_crtc to struct tegra_dc is made safer to
prevent potential segmentation faults.
----------------------------------------------------------------
Dan Carpenter (1):
drm/tegra: return -EFAULT if copy_from_user() fails
Olof Johansson (1):
gpu: host1x: Silence a few warnings with LPAE=y
Thierry Reding (6):
drm/tegra: Make CRTC upcasting safer
drm/tegra: Tightly bind RGB output to DC
drm/tegra: Fix address space mismatches
drm/tegra: Make tegra_drm_driver static
drm/tegra: Force cast to __iomem to make sparse happy
gpu: host1x: Fix a few sparse warnings
drivers/gpu/drm/tegra/drm.c | 34 +++++++++++++++++++---------------
drivers/gpu/drm/tegra/drm.h | 2 +-
drivers/gpu/drm/tegra/fb.c | 2 +-
drivers/gpu/drm/tegra/rgb.c | 11 +++++++----
drivers/gpu/host1x/bus.c | 5 +++--
drivers/gpu/host1x/hw/cdma_hw.c | 4 ++--
drivers/gpu/host1x/hw/debug_hw.c | 4 ++--
7 files changed, 35 insertions(+), 27 deletions(-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-12-03 9:26 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=20131203092612.GA21178@ulmo.nvidia.com \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox