dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	airlied@gmail.com, daniel.vetter@ffwll.ch
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] amdgpu drm-fixes-5.4
Date: Thu, 14 Nov 2019 17:13:54 -0500	[thread overview]
Message-ID: <20191114221354.3914-1-alexander.deucher@amd.com> (raw)

Hi Dave, Daniel,

Just one fix for 5.4.

The following changes since commit 31f4f5b495a62c9a8b15b1c3581acd5efeb9af8c:

  Linux 5.4-rc7 (2019-11-10 16:17:15 -0800)

are available in the Git repository at:

  git://people.freedesktop.org/~agd5f/linux tags/drm-fixes-5.4-2019-11-14

for you to fetch changes up to a84fddb16d9bdcb2e40b26aa53a4e4703839298a:

  drm/amdgpu: fix null pointer deref in firmware header printing (2019-11-14 16:53:19 -0500)

----------------------------------------------------------------
drm-fixes-5.4-2019-11-14:

amdgpu:
- Fix a potential crash in firmware parsing

----------------------------------------------------------------
Xiaojie Yuan (1):
      drm/amdgpu: fix null pointer deref in firmware header printing

 drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 38 ++++++++++++++-------------------
 1 file changed, 16 insertions(+), 22 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-11-14 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 22:13 Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-20 23:51 [pull] amdgpu drm-fixes-5.4 Alex Deucher
2019-10-24  3:18 Alex Deucher
2019-10-24  3:18 ` Alex Deucher
2019-10-10  3:10 Alex Deucher
2019-10-02 20:49 Alex Deucher
2019-09-25 21:35 Alex Deucher
2019-09-19 15:38 Alex Deucher

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=20191114221354.3914-1-alexander.deucher@amd.com \
    --to=alexdeucher@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --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