public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic/drm-fixes for 4.2
Date: Thu, 9 Jul 2015 16:17:36 +0200	[thread overview]
Message-ID: <20150709141736.GA6573@phenom.ffwll.local> (raw)

Hi Dave,

Non-i915 fixes I picked up in your absence: kerneldoc + 2x cc: stable. The
rockchip fix is just in here to make sure it won't get lost, I kept it
since I didn't yet see a rockchip fixes pull nor confirmation from Mark
that he pulled it into his tree.

Cheers, Daniel


The following changes since commit e24ff467e12e1560de753313976c46e84fa6306a:

  drm/crtc: Fix edid length computation (2015-07-04 00:52:34 +0200)

are available in the git repository at:

  git://anongit.freedesktop.org/drm-intel tags/topic/drm-fixes-2015-07-09

for you to fetch changes up to d4acc1651588835b802a2049f4f3a2adcc1af750:

  Documentation: drm: Fix tablulation in KMS properties table (2015-07-07 22:42:58 +0200)

----------------------------------------------------------------
Daniel Kurtz (1):
      drm/rockchip: use drm_gem_mmap helpers

Graham Whaley (1):
      Documentation: drm: Fix tablulation in KMS properties table

Zhao Junwang (1):
      drm: add a check for x/y in drm_mode_setcrtc

 Documentation/DocBook/drm.tmpl              |  2 +-
 drivers/gpu/drm/drm_crtc.c                  |  7 ++-
 drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 67 +++++++++++++++--------------
 3 files changed, 40 insertions(+), 36 deletions(-)

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2015-07-09 14:17 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=20150709141736.GA6573@phenom.ffwll.local \
    --to=daniel.vetter@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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