mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: Xiaofeng Cao <cxfcosmos@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	huyue2@yulong.com, Xiaofeng Cao <caoxiaofeng@yulong.com>
Subject: Re: [PATCH] Rectify spelling
Date: Mon, 22 Mar 2021 15:15:38 +0100	[thread overview]
Message-ID: <20210322141538.imsggoeo3zhspwvz@earth.universe> (raw)
In-Reply-To: <20210311115735.1103-1-cxfcosmos@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3106 bytes --]

Hi,

On Thu, Mar 11, 2021 at 07:57:35PM +0800, Xiaofeng Cao wrote:
> Change  'stanalone'      to  'standalone'
> Change  'mesaurement'    to  'measurement'
> Change  'nonvilatile'    to  'nonvolatile'
> Change  'unical'         to  'unique'
> Change  'unaccesable'    to  'unaccessible'
> Change  'correcpondent'  to  'correspond'
> 
> Signed-off-by: Xiaofeng Cao <caoxiaofeng@yulong.com>
> ---

Thanks, queued. Please improve your patch subjects in the
future and use PATCHv2 instead of PATCH when sending a new
version.

-- Sebastian

>  drivers/power/supply/max1721x_battery.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/power/supply/max1721x_battery.c b/drivers/power/supply/max1721x_battery.c
> index 1b1a36f8e929..473e53cd2801 100644
> --- a/drivers/power/supply/max1721x_battery.c
> +++ b/drivers/power/supply/max1721x_battery.c
> @@ -1,6 +1,6 @@
>  /*
>   * 1-Wire implementation for Maxim Semiconductor
> - * MAX7211/MAX17215 stanalone fuel gauge chip
> + * MAX7211/MAX17215 standalone fuel gauge chip
>   *
>   * Copyright (C) 2017 Radioavionica Corporation
>   * Author: Alex A. Mihaylov <minimumlaw@rambler.ru>
> @@ -28,7 +28,7 @@
>  /* Number of valid register addresses in W1 mode */
>  #define MAX1721X_MAX_REG_NR	0x1EF
>  
> -/* Factory settings (nonvilatile registers) (W1 specific) */
> +/* Factory settings (nonvolatile registers) (W1 specific) */
>  #define MAX1721X_REG_NRSENSE	0x1CF	/* RSense in 10^-5 Ohm */
>  /* Strings */
>  #define MAX1721X_REG_MFG_STR	0x1CC
> @@ -105,7 +105,7 @@ static inline int max172xx_temperature_to_ps(unsigned int reg)
>  /*
>   * Calculating current registers resolution:
>   *
> - * RSense stored in 10^-5 Ohm, so mesaurment voltage must be
> + * RSense stored in 10^-5 Ohm, so measurement voltage must be
>   * in 10^-11 Volts for get current in uA.
>   * 16 bit current reg fullscale +/-51.2mV is 102400 uV.
>   * So: 102400 / 65535 * 10^5 = 156252
> @@ -137,7 +137,7 @@ static int max1721x_battery_get_property(struct power_supply *psy,
>  		/*
>  		 * POWER_SUPPLY_PROP_PRESENT will always readable via
>  		 * sysfs interface. Value return 0 if battery not
> -		 * present or unaccesable via W1.
> +		 * present or unaccessible via W1.
>  		 */
>  		val->intval =
>  			regmap_read(info->regmap, MAX172XX_REG_STATUS,
> @@ -334,9 +334,9 @@ static int devm_w1_max1721x_add_device(struct w1_slave *sl)
>  
>  	/*
>  	 * power_supply class battery name translated from W1 slave device
> -	 * unical ID (look like 26-0123456789AB) to "max1721x-0123456789AB\0"
> -	 * so, 26 (device family) correcpondent to max1721x devices.
> -	 * Device name still unical for any numbers connected devices.
> +	 * unique ID (look like 26-0123456789AB) to "max1721x-0123456789AB\0"
> +	 * so, 26 (device family) correspond to max1721x devices.
> +	 * Device name still unique for any number of connected devices.
>  	 */
>  	snprintf(info->name, sizeof(info->name),
>  		"max1721x-%012X", (unsigned int)sl->reg_num.id);
> -- 
> 2.25.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-22 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 11:57 Xiaofeng Cao
2021-03-22 14:15 ` Sebastian Reichel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-11 11:29 Xiaofeng Cao

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=20210322141538.imsggoeo3zhspwvz@earth.universe \
    --to=sre@kernel.org \
    --cc=caoxiaofeng@yulong.com \
    --cc=cxfcosmos@gmail.com \
    --cc=huyue2@yulong.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    /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®