All of 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.2
Date: Wed, 15 Feb 2023 23:11:22 -0500	[thread overview]
Message-ID: <20230216041122.7714-1-alexander.deucher@amd.com> (raw)

Hi Dave, Daniel,

A couple of warning fixes for 6.2.

The following changes since commit ceaa837f96adb69c0df0397937cd74991d5d821a:

  Linux 6.2-rc8 (2023-02-12 14:10:17 -0800)

are available in the Git repository at:

  https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.2-2023-02-15

for you to fetch changes up to 2a00299e7447395d0898e7c6214817c06a61a8e8:

  drm/amd/display: Fail atomic_check early on normalize_zpos error (2023-02-15 22:46:42 -0500)

----------------------------------------------------------------
amd-drm-fixes-6.2-2023-02-15:

amdgpu:
- Fix GC11.x suspend warning
- Fix display warning

----------------------------------------------------------------
Jack Xiao (1):
      drm/amd/amdgpu: fix warning during suspend

Leo Li (1):
      drm/amd/display: Fail atomic_check early on normalize_zpos error

 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c        | 3 +++
 drivers/gpu/drm/amd/amdgpu/mes_v11_0.c            | 2 +-
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 6 +++++-
 3 files changed, 9 insertions(+), 2 deletions(-)

             reply	other threads:[~2023-02-16  4:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  4:11 Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-09 17:45 [pull] amdgpu drm-fixes-6.2 Alex Deucher
2023-02-09  4:53 Alex Deucher
2023-02-02  4:23 Alex Deucher
2023-01-19 19:59 Alex Deucher
2022-12-15 22:49 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=20230216041122.7714-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.