From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
lee.jones@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: mfd: Spelling fixes in the file max77620.c
Date: Fri, 5 Feb 2021 09:14:11 -0800 [thread overview]
Message-ID: <eaf48b69-3caf-dfc3-e54b-ff1f159e2efd@infradead.org> (raw)
In-Reply-To: <20210205085456.369049-1-unixbhaskar@gmail.com>
On 2/5/21 12:54 AM, Bhaskar Chowdhury wrote:
>
>
> s/Teminology/Terminology/
> s/confguration/configuration/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/mfd/max77620.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mfd/max77620.c b/drivers/mfd/max77620.c
> index fec2096474ad..429f7fbe92bc 100644
> --- a/drivers/mfd/max77620.c
> +++ b/drivers/mfd/max77620.c
> @@ -10,7 +10,7 @@
> * Mallikarjun Kasoju <mkasoju@nvidia.com>
> */
>
> -/****************** Teminology used in driver ********************
> +/****************** Terminology used in driver ********************
> * Here are some terminology used from datasheet for quick reference:
> * Flexible Power Sequence (FPS):
> * The Flexible Power Sequencer (FPS) allows each regulator to power up under
> @@ -20,7 +20,7 @@
> * be programmed to be part of a sequence allowing external regulators to be
> * sequenced along with internal regulators. 32KHz clock can be programmed to
> * be part of a sequence.
> - * There is 3 FPS confguration registers and all resources are configured to
> + * There is 3 FPS configuration registers and all resources are configured to
> * any of these FPS or no FPS.
> */
>
> --
> 2.30.0
>
--
~Randy
prev parent reply other threads:[~2021-02-05 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 8:54 Bhaskar Chowdhury
2021-02-05 17:14 ` Randy Dunlap [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=eaf48b69-3caf-dfc3-e54b-ff1f159e2efd@infradead.org \
--to=rdunlap@infradead.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.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®