From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
robdclark@gmail.com, sean@poorly.run, airlied@linux.ie,
daniel@ffwll.ch, khsieh@codeaurora.org, tanmay@codeaurora.org,
chandanu@codeaurora.org, swboyd@chromium.org,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: Fixed couple of typos
Date: Thu, 18 Mar 2021 11:21:55 -0700 [thread overview]
Message-ID: <d3facf30-2a60-46f2-caa0-af63d3a52dd1@infradead.org> (raw)
In-Reply-To: <20210318062650.19886-1-unixbhaskar@gmail.com>
On 3/17/21 11:26 PM, Bhaskar Chowdhury wrote:
> s/modueles/modules/ ....two different places
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/gpu/drm/msm/dp/dp_power.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/dp/dp_power.h b/drivers/gpu/drm/msm/dp/dp_power.h
> index 7d0327bbc0d5..e3f959ffae12 100644
> --- a/drivers/gpu/drm/msm/dp/dp_power.h
> +++ b/drivers/gpu/drm/msm/dp/dp_power.h
> @@ -88,7 +88,7 @@ int dp_power_client_init(struct dp_power *power);
> * return: 0 for success, error for failure.
> *
> * This API will de-initialize the DisplayPort's clocks and regulator
> - * modueles.
> + * modules.
> */
> void dp_power_client_deinit(struct dp_power *power);
>
> @@ -100,7 +100,7 @@ void dp_power_client_deinit(struct dp_power *power);
> *
> * This API will configure the DisplayPort's power module and provides
> * methods to be called by the client to configure the power related
> - * modueles.
> + * modules.
> */
> struct dp_power *dp_power_get(struct device *dev, struct dp_parser *parser);
>
> --
--
~Randy
next prev parent reply other threads:[~2021-03-18 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 6:26 Bhaskar Chowdhury
2021-03-18 18:21 ` Randy Dunlap [this message]
2021-03-23 3:24 ` Stephen Boyd
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=d3facf30-2a60-46f2-caa0-af63d3a52dd1@infradead.org \
--to=rdunlap@infradead.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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=tanmay@codeaurora.org \
--cc=unixbhaskar@gmail.com \
/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®