From: abhinavk@codeaurora.org
To: Lee Jones <lee.jones@linaro.org>
Cc: freedreno@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Kuogee Hsieh <khsieh@codeaurora.org>,
Rob Clark <robdclark@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Sean Paul <sean@poorly.run>,
Chandan Uddaraju <chandanu@codeaurora.org>
Subject: Re: [Freedreno] [RESEND 14/26] drm/msm/dp/dp_link: Fix some potential doc-rot
Date: Wed, 02 Jun 2021 10:33:56 -0700 [thread overview]
Message-ID: <b668e09546c0ce86d90346f99f40853a@codeaurora.org> (raw)
On 2021-06-02 07:32, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/msm/dp/dp_link.c:374: warning: expecting prototype
> for dp_parse_video_pattern_params(). Prototype was for
> dp_link_parse_video_pattern_params() instead
> drivers/gpu/drm/msm/dp/dp_link.c:573: warning: expecting prototype
> for dp_parse_phy_test_params(). Prototype was for
> dp_link_parse_phy_test_params() instead
> drivers/gpu/drm/msm/dp/dp_link.c:975: warning: expecting prototype
> for dp_link_process_downstream_port_status_change(). Prototype was for
> dp_link_process_ds_port_status_change() instead
>
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: Sean Paul <sean@poorly.run>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Chandan Uddaraju <chandanu@codeaurora.org>
> Cc: Kuogee Hsieh <khsieh@codeaurora.org>
> Cc: linux-arm-msm@vger.kernel.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: freedreno@lists.freedesktop.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Reviewed-by: Abhinav Kumar <abhinavk@codeaurora.org>
> ---
> drivers/gpu/drm/msm/dp/dp_link.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/dp/dp_link.c
> b/drivers/gpu/drm/msm/dp/dp_link.c
> index be986da78c4a5..1099604bd1c86 100644
> --- a/drivers/gpu/drm/msm/dp/dp_link.c
> +++ b/drivers/gpu/drm/msm/dp/dp_link.c
> @@ -364,7 +364,7 @@ static int dp_link_parse_timing_params3(struct
> dp_link_private *link,
> }
>
> /**
> - * dp_parse_video_pattern_params() - parses video pattern parameters
> from DPCD
> + * dp_link_parse_video_pattern_params() - parses video pattern
> parameters from DPCD
> * @link: Display Port Driver data
> *
> * Returns 0 if it successfully parses the video link pattern and the
> link
> @@ -563,7 +563,7 @@ static int
> dp_link_parse_link_training_params(struct dp_link_private *link)
> }
>
> /**
> - * dp_parse_phy_test_params() - parses the phy link parameters
> + * dp_link_parse_phy_test_params() - parses the phy link parameters
> * @link: Display Port Driver data
> *
> * Parses the DPCD (Byte 0x248) for the DP PHY link pattern that is
> being
> @@ -961,7 +961,7 @@ static int
> dp_link_process_link_status_update(struct dp_link_private *link)
> }
>
> /**
> - * dp_link_process_downstream_port_status_change() - process port
> status changes
> + * dp_link_process_ds_port_status_change() - process port status
> changes
> * @link: Display Port Driver data
> *
> * This function will handle downstream port updates that are
> initiated by
reply other threads:[~2021-06-02 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b668e09546c0ce86d90346f99f40853a@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=chandanu@codeaurora.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=khsieh@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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