From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Rob Clark <robdclark@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] drm/msm/dp: Fix spelling mistake "Capabiity" -> "Capability"
Date: Tue, 14 Mar 2023 09:35:56 -0700 [thread overview]
Message-ID: <9dc6c74f-8982-0ccb-af1b-e6ef22276886@quicinc.com> (raw)
In-Reply-To: <20230314082050.26331-1-colin.i.king@gmail.com>
On 3/14/2023 1:20 AM, Colin Ian King wrote:
> There is a spelling mistake in a drm_dbg_dp message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
> ---
> drivers/gpu/drm/msm/dp/dp_link.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/dp/dp_link.c b/drivers/gpu/drm/msm/dp/dp_link.c
> index 5a4817ac086f..42427129acea 100644
> --- a/drivers/gpu/drm/msm/dp/dp_link.c
> +++ b/drivers/gpu/drm/msm/dp/dp_link.c
> @@ -1090,7 +1090,7 @@ int dp_link_process_request(struct dp_link *dp_link)
> } else if (dp_link_read_psr_error_status(link)) {
> DRM_ERROR("PSR IRQ_HPD received\n");
> } else if (dp_link_psr_capability_changed(link)) {
> - drm_dbg_dp(link->drm_dev, "PSR Capabiity changed");
> + drm_dbg_dp(link->drm_dev, "PSR Capability changed");
> } else {
> ret = dp_link_process_link_status_update(link);
> if (!ret) {
next prev parent reply other threads:[~2023-03-14 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 8:20 Colin Ian King
2023-03-14 16:35 ` Abhinav Kumar [this message]
2023-03-28 22:37 ` Dmitry Baryshkov
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=9dc6c74f-8982-0ccb-af1b-e6ef22276886@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.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
all inboxes | Powered by JetHome®