All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Pan Xinhui" <Xinhui.Pan@amd.com>,
	jani.nikula@intel.com
Subject: [PATCH 0/3] drm/mst & drm/amd/display: switch to using guid_t
Date: Fri, 31 May 2024 15:00:30 +0300	[thread overview]
Message-ID: <cover.1717156601.git.jani.nikula@intel.com> (raw)

We have a guid_t type for GUIDs, switch to using it instead of hand
rolling buffers. Convert to guid_gen() in separate patches to pinpoint
the functional changes.

BR,
Jani.

Jani Nikula (3):
  drm/mst: switch to guid_t type for GUID
  drm/mst: switch to guid_gen() to generate valid GUIDs
  drm/amd/display: switch to guid_gen() to generate valid GUIDs

 .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 23 ++++---
 drivers/gpu/drm/display/drm_dp_mst_topology.c | 67 ++++++++++---------
 include/drm/display/drm_dp_mst_helper.h       | 12 ++--
 3 files changed, 52 insertions(+), 50 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-05-31 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 12:00 Jani Nikula [this message]
2024-05-31 12:00 ` [PATCH 1/3] drm/mst: switch to guid_t type for GUID Jani Nikula
2024-05-31 12:00 ` [PATCH 2/3] drm/mst: switch to guid_gen() to generate valid GUIDs Jani Nikula
2024-05-31 12:00 ` [PATCH 3/3] drm/amd/display: " Jani Nikula
2024-05-31 14:50 ` ✗ Fi.CI.SPARSE: warning for drm/mst & drm/amd/display: switch to using guid_t Patchwork
2024-05-31 14:56 ` ✓ Fi.CI.BAT: success " Patchwork
2024-06-01 20:05 ` ✗ Fi.CI.IGT: failure " Patchwork

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=cover.1717156601.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.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 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.