dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexander.deucher@amd.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-6.6
Date: Thu, 19 Oct 2023 21:24:17 -0400	[thread overview]
Message-ID: <20231020012417.4876-1-alexander.deucher@amd.com> (raw)

Hi Dave, Sima,

Fixes for 6.6.

The following changes since commit 58720809f52779dc0f08e53e54b014209d13eebb:

  Linux 6.6-rc6 (2023-10-15 13:34:39 -0700)

are available in the Git repository at:

  https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.6-2023-10-19

for you to fetch changes up to 316baf09d355aec1179981b6dfe28eba50c5ee5b:

  drm/amdgpu: Reserve fences for VM update (2023-10-19 18:56:57 -0400)

----------------------------------------------------------------
amd-drm-fixes-6.6-2023-10-19:

amdgpu:
- Fix possible NULL pointer dereference
- Avoid possible BUG_ON in GPUVM updates

----------------------------------------------------------------
Felix Kuehling (2):
      drm/amdgpu: Fix possible null pointer dereference
      drm/amdgpu: Reserve fences for VM update

 drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 5 ++++-
 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c      | 3 ++-
 2 files changed, 6 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-10-20  1:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  1:24 Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-26  3:54 [pull] amdgpu drm-fixes-6.6 Alex Deucher
2023-10-12  2:56 Alex Deucher
2023-10-05  3:43 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=20231020012417.4876-1-alexander.deucher@amd.com \
    --to=alexander.deucher@amd.com \
    --cc=airlied@gmail.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