dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: [PULL] random pile of drm core patches
Date: Mon, 17 Mar 2014 11:26:58 +0100	[thread overview]
Message-ID: <20140317102658.GT30571@phenom.ffwll.local> (raw)

Hi Dave,

Here's a pull for -next with some random drm-core patches. I've also
thrown the use-after-free fix on top, but that should go into -fixes, too.

Feel free to pull or slurp in the patches you want from patchwork
yourself.

Cheers, Daniel

The following changes since commit 4d538b79197901fecc42e746d515d07fd1089b62:

  Merge branch 'drm-next-3.15' of git://people.freedesktop.org/~deathsimple/linux into drm-next (2014-02-27 14:39:30 +1000)

are available in the git repository at:


  ssh://git.freedesktop.org/git/drm-intel topic/core-stuff

for you to fetch changes up to c94adc4a65c67a79f0d19285bf5c32fe4c00176f:

  drm: Fix use-after-free in the shadow-attache exit code (2014-03-17 11:23:31 +0100)

----------------------------------------------------------------
Damien Lespiau (1):
      drm: Check if the allocation has succeeded before dereferencing newmode

Daniel Drake (1):
      drm/edid: request HDMI underscan by default

Daniel Vetter (1):
      drm: Fix use-after-free in the shadow-attache exit code

Ville Syrjälä (1):
      drm/fb-helper: Use drm_fb_helper_restore_fbdev_mode() in drm_fb_helper_set_par()

Xiubo Li (1):
      drm/fb-helper: Do the 'max_conn_count' zero check

 drivers/gpu/drm/drm_edid.c      |  4 ++++
 drivers/gpu/drm/drm_fb_helper.c | 13 ++++---------
 drivers/gpu/drm/drm_pci.c       |  2 +-
 3 files changed, 9 insertions(+), 10 deletions(-)
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

                 reply	other threads:[~2014-03-17 10:27 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=20140317102658.GT30571@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@gmail.com \
    --cc=dri-devel@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