From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
imre.deak@intel.com, Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Lyude Paul <lyude@redhat.com>
Subject: Re: [PATCH 0/3] drm/dp: extract payload helpers
Date: Wed, 27 Nov 2024 15:13:17 +0200 [thread overview]
Message-ID: <87sercx1jm.fsf@intel.com> (raw)
In-Reply-To: <cover.1731942780.git.jani.nikula@intel.com>
On Mon, 18 Nov 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> Add some mst topology manager independent payload helpers.
Cc: maintainers, Lyude, are we good to go with this?
BR,
Jani.
>
> Jani Nikula (3):
> drm/dp: extract drm_dp_dpcd_poll_act_handled()
> drm/dp: extract drm_dp_dpcd_write_payload()
> drm/dp: extract drm_dp_dpcd_clear_payload()
>
> drivers/gpu/drm/display/drm_dp_helper.c | 124 +++++++++++++++++-
> drivers/gpu/drm/display/drm_dp_mst_topology.c | 88 +------------
> include/drm/display/drm_dp_helper.h | 5 +
> 3 files changed, 133 insertions(+), 84 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-11-27 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 15:14 [PATCH 0/3] drm/dp: extract payload helpers Jani Nikula
2024-11-18 15:14 ` [PATCH 1/3] drm/dp: extract drm_dp_dpcd_poll_act_handled() Jani Nikula
2024-11-20 14:59 ` Imre Deak
2024-11-20 15:18 ` Imre Deak
2024-11-22 12:22 ` Jani Nikula
2024-11-22 14:07 ` Imre Deak
2024-11-18 15:14 ` [PATCH 2/3] drm/dp: extract drm_dp_dpcd_write_payload() Jani Nikula
2024-11-20 15:07 ` Imre Deak
2024-11-18 15:14 ` [PATCH 3/3] drm/dp: extract drm_dp_dpcd_clear_payload() Jani Nikula
2024-11-20 15:09 ` Imre Deak
2024-11-27 13:13 ` Jani Nikula [this message]
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=87sercx1jm.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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).