mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	sre@kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: supply: Trivial spelling fixes
Date: Tue, 23 Mar 2021 10:47:32 -0700	[thread overview]
Message-ID: <1f35f9ff-ae16-443c-b18e-40f32013ccdb@infradead.org> (raw)
In-Reply-To: <20210323124206.24813-1-unixbhaskar@gmail.com>

On 3/23/21 5:42 AM, Bhaskar Chowdhury wrote:
> Few trivial spelling fixes .
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>


> ---
>  drivers/power/supply/max17042_battery.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/power/supply/max17042_battery.c b/drivers/power/supply/max17042_battery.c
> index 79d4b5988360..1d7326cd8fc6 100644
> --- a/drivers/power/supply/max17042_battery.c
> +++ b/drivers/power/supply/max17042_battery.c
> @@ -131,7 +131,7 @@ static int max17042_get_status(struct max17042_chip *chip, int *status)
>  	 *
>  	 * When this cycle the battery gets charged to a higher (calculated)
>  	 * capacity then the previous cycle then FullCAP will get updated
> -	 * contineously once end-of-charge detection kicks in, so allow the
> +	 * continuously once end-of-charge detection kicks in, so allow the
>  	 * 2 to differ a bit.
>  	 */
> 
> @@ -739,7 +739,7 @@ static void max17042_load_new_capacity_params(struct max17042_chip *chip)
> 
>  /*
>   * Block write all the override values coming from platform data.
> - * This function MUST be called before the POR initialization proceedure
> + * This function MUST be called before the POR initialization procedure
>   * specified by maxim.
>   */
>  static inline void max17042_override_por_values(struct max17042_chip *chip)
> @@ -811,7 +811,7 @@ static int max17042_init_chip(struct max17042_chip *chip)
>  	 */
>  	msleep(500);
> 
> -	/* Initialize configaration */
> +	/* Initialize configuration */
>  	max17042_write_config_regs(chip);
> 
>  	/* write cell characterization data */
> @@ -855,7 +855,7 @@ static void max17042_set_soc_threshold(struct max17042_chip *chip, u16 off)
>  	struct regmap *map = chip->regmap;
>  	u32 soc, soc_tr;
> 
> -	/* program interrupt thesholds such that we should
> +	/* program interrupt thresholds such that we should
>  	 * get interrupt for every 'off' perc change in the soc
>  	 */
>  	regmap_read(map, MAX17042_RepSOC, &soc);
> --


-- 
~Randy


      reply	other threads:[~2021-03-23 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 12:42 Bhaskar Chowdhury
2021-03-23 17:47 ` 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=1f35f9ff-ae16-443c-b18e-40f32013ccdb@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@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®