dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mikita Lipski <mlipski@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] drm/dp_mst: fix documentation of drm_dp_mst_add_affected_dsc_crtcs
Date: Thu, 9 Jan 2020 08:53:23 -0500	[thread overview]
Message-ID: <b2a3f7d9-5939-eec9-6f29-7b9115ad0679@amd.com> (raw)
In-Reply-To: <20200109032412.364214-1-alexander.deucher@amd.com>

Thank you,
Reviewed-by: Mikita Lipski <mikita.lipski@amd.com>

On 1/8/20 10:24 PM, Alex Deucher wrote:
> the parameter is the mst manager, not the port.
> 
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>   drivers/gpu/drm/drm_dp_mst_topology.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 7e9b9b7e50cf..a4be2f825899 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -4781,7 +4781,7 @@ drm_dp_mst_atomic_check_vcpi_alloc_limit(struct drm_dp_mst_topology_mgr *mgr,
>   /**
>    * drm_dp_mst_add_affected_dsc_crtcs
>    * @state: Pointer to the new struct drm_dp_mst_topology_state
> - * @port: Port pointer of connector with new state
> + * @mgr: MST topology manager
>    *
>    * Whenever there is a change in mst topology
>    * DSC configuration would have to be recalculated
> 

-- 
Thanks,
Mikita Lipski
Software Engineer, AMD
mikita.lipski@amd.com
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-01-09 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  3:24 [PATCH] drm/dp_mst: fix documentation of drm_dp_mst_add_affected_dsc_crtcs Alex Deucher
2020-01-09 13:53 ` Mikita Lipski [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=b2a3f7d9-5939-eec9-6f29-7b9115ad0679@amd.com \
    --to=mlipski@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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;
as well as URLs for NNTP newsgroup(s).