intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dim-tools@lists.freedesktop.org,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Sean Paul <sean@poorly.run>
Subject: [PULL] drm-misc-next-fixes
Date: Wed, 2 Jan 2019 18:26:09 +0100	[thread overview]
Message-ID: <46c4dbcd-dc23-7b46-fda9-16fe33e6ceef@linux.intel.com> (raw)

drm-misc-next-fixes-2019-01-02:
Fixes for v4.21:
- Fix null pointer dereference on null state pointer.
- Fix leaking damage clip when destroying plane state.
The following changes since commit 2e6e902d185027f8e3cb8b7305238f7e35d6a436:

  Linux 4.20-rc4 (2018-11-25 14:19:31 -0800)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2019-01-02

for you to fetch changes up to c75ff001f4fe21a8c9f15aad799a8949aea109f7:

  drm: Put damage blob when destroy plane state (2018-12-24 11:53:50 +0100)

----------------------------------------------------------------
Fixes for v4.21:
- Fix null pointer dereference on null state pointer.
- Fix leaking damage clip when destroying plane state.

----------------------------------------------------------------
Colin Ian King (1):
      drm: fix null pointer dereference on null state pointer

Deepak Rawat (1):
      drm: Put damage blob when destroy plane state

 drivers/gpu/drm/drm_atomic_state_helper.c | 3 +++
 drivers/gpu/drm/drm_damage_helper.c       | 3 ++-
 2 files changed, 5 insertions(+), 1 deletion(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-01-02 17:26 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 17:26 Maarten Lankhorst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-02 12:23 [PULL] drm-misc-next-fixes Thomas Zimmermann
2025-09-25  6:42 Thomas Zimmermann
2025-09-18  6:45 Thomas Zimmermann
2025-08-12  6:47 Thomas Zimmermann
2025-07-24  6:52 Maxime Ripard
2025-06-05 17:02 Maarten Lankhorst
2025-04-04  6:51 Thomas Zimmermann
2025-03-27 14:18 Thomas Zimmermann
2025-03-13 18:01 Thomas Zimmermann
2025-01-24 15:25 Maarten Lankhorst
2025-01-24 16:09 ` Simona Vetter
2025-01-16  8:45 Maxime Ripard
2024-11-28 13:01 Maarten Lankhorst
2024-09-05 11:38 Thomas Zimmermann
2024-07-25 14:59 Maxime Ripard
2024-07-19  7:39 Maxime Ripard
2024-07-11 11:43 Maxime Ripard
2024-06-06 22:12 Maarten Lankhorst
2024-05-23  4:41 Maarten Lankhorst
2024-05-16 15:00 Maarten Lankhorst
2024-05-08 10:36 Maarten Lankhorst
2024-03-21 16:19 Thomas Zimmermann
2024-03-14  8:28 Thomas Zimmermann
2024-03-07 12:46 Thomas Zimmermann
2024-02-29  8:53 Thomas Zimmermann
2024-01-19 12:13 Maxime Ripard
2024-01-11 10:11 Maxime Ripard
2024-01-04 14:45 Maxime Ripard
2023-12-21  8:36 Maxime Ripard
2019-11-20 20:49 Sean Paul
2019-11-13 21:10 Sean Paul
2019-11-06 20:27 Sean Paul
2019-09-23 16:09 Maxime Ripard
2019-09-18 14:09 Maxime Ripard
2019-09-06  7:05 Maxime Ripard
2019-07-18 15:14 Sean Paul
2019-07-12  8:33 Maarten Lankhorst
2019-06-27 13:03 Maarten Lankhorst
2019-05-15 20:17 Sean Paul
2019-05-08 20:51 Sean Paul
2019-05-01 19:09 Sean Paul
2019-04-24 21:06 Sean Paul
2019-03-13 19:21 Maxime Ripard
2019-03-06 10:54 Maxime Ripard
2018-10-31 20:19 Sean Paul
2018-10-17 20:07 Sean Paul
2018-10-10 20:39 Sean Paul
2018-08-22 19:38 Sean Paul
2018-08-02 11:17 Gustavo Padovan
2018-06-15  8:11 Maarten Lankhorst
2018-05-31  8:11 Maarten Lankhorst
2018-04-11 14:03 Sean Paul
2018-04-04 19:14 Sean Paul
2018-03-28 19:13 Sean Paul
2018-01-31 15:09 Gustavo Padovan
2018-01-18 17:09 Gustavo Padovan
2017-11-23 19:45 Daniel Vetter
2017-11-08 13:00 Daniel Vetter
2017-11-07 13:44 Daniel Vetter
2017-08-28 21:22 Sean Paul
2017-07-10 19:58 Sean Paul
2017-06-27 20:53 Sean Paul
2017-04-20 20:11 Sean Paul
2017-04-20 21:50 ` Daniel Vetter
2017-04-21 15:29   ` Sumit Semwal
2017-04-21 18:10   ` Sean Paul
2017-04-12 22:58 Sean Paul
2017-02-27 15:52 Daniel Vetter
2017-02-15 13:54 Jani Nikula
2017-02-16  9:39 ` Jani Nikula
2017-02-09  8:43 Daniel Vetter
2016-12-10 21:52 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=46c4dbcd-dc23-7b46-fda9-16fe33e6ceef@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sean@poorly.run \
    /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;
as well as URLs for NNTP newsgroup(s).