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/core-stuff
Date: Wed, 10 Dec 2014 13:50:58 +0100	[thread overview]
Message-ID: <20141210125058.GA16704@phenom.ffwll.local> (raw)

Hi Dave,

Decided to send a pull request for my misc drm branch because of teh
memset patch from Thierry for drm_*_cleanup functions (fixes drivers using
deferred probe) and the patch from Takashi. Everything else fairly
trivial.

Cheers, Daniel


The following changes since commit e5b5341c28c66a122982d3d8822a4f9a0938f923:

  drm/atomic: clear plane's CRTC and FB when shutting down (2014-11-27 15:39:11 +0100)

are available in the git repository at:

  git://anongit.freedesktop.org/drm-intel tags/topic/core-stuff-2014-12-10

for you to fetch changes up to a18c0af171bfb875012da26f23df051004726973:

  drm: Zero out DRM object memory upon cleanup (2014-12-10 12:05:56 +0100)

----------------------------------------------------------------
Martin Peres (2):
      drm: fix a word repetition in a comment
      drm: fix a typo in a comment

Sean Paul (1):
      drm/Documentation: Fix rowspan value in drm-kms-properties

Stefan Brüns (3):
      drm/edid: move drm_edid_is_zero to top, make edid argument const
      drm/edid: shorten log output in case of all zeroes edid block
      drm/edid: new drm_edid_block_checksum helper function V3

Takashi Iwai (1):
      drm: Fix memory leak at error path of drm_read()

Thierry Reding (2):
      drm/edid: Restore kerneldoc consistency
      drm: Zero out DRM object memory upon cleanup

 Documentation/DocBook/drm.tmpl |  2 +-
 drivers/gpu/drm/drm_crtc.c     | 13 +++++++++++--
 drivers/gpu/drm/drm_edid.c     | 42 +++++++++++++++++++++++++++---------------
 drivers/gpu/drm/drm_fops.c     |  1 +
 drivers/gpu/drm/drm_irq.c      |  2 +-
 5 files changed, 41 insertions(+), 19 deletions(-)

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-12-10 12:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 12:50 Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-23 15:56 [PULL] topic/core-stuff Daniel Vetter
2014-11-28 13:27 Daniel Vetter
2014-11-05 13:05 Daniel Vetter
2014-10-03  8:42 Daniel Vetter
2014-09-29  7:18 Daniel Vetter
2014-09-24 10:24 Daniel Vetter
2014-09-24 16:24 ` Ilia Mirkin
2014-09-24 17:59   ` Daniel Vetter
2014-09-24 21:07     ` Dave Airlie
2014-09-24 19:43 ` Daniel Vetter
2014-09-15  8:58 Daniel Vetter
2014-09-12 17:32 Daniel Vetter
2014-09-12 21:05 ` Dave Airlie
2014-08-05 15:24 Daniel Vetter
2014-07-18 16:37 Daniel Vetter
2014-06-30 11:43 Jani Nikula
2014-06-02  8:09 Daniel Vetter
2014-05-05  9:19 Daniel Vetter
2014-05-14 18:30 ` Daniel Vetter

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=20141210125058.GA16704@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