linux-kernel - Re: [PATCH] regulator: Proofread documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53FB6B26.3030906@infradead.org>
Date:	Mon, 25 Aug 2014 09:58:14 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Geert Uytterhoeven <geert+renesas@...der.be>,
	Liam Girdwood <lgirdwood@...il.com>,
	Mark Brown <broonie@...nel.org>
CC:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Proofread documentation

On 08/25/14 01:47, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
>  Documentation/power/regulator/consumer.txt  | 7 ++++---
>  Documentation/power/regulator/design.txt    | 8 ++++----
>  Documentation/power/regulator/machine.txt   | 4 ++--
>  Documentation/power/regulator/overview.txt  | 6 +++---
>  Documentation/power/regulator/regulator.txt | 6 +++---
>  5 files changed, 16 insertions(+), 15 deletions(-)
> 
> diff --git a/Documentation/power/regulator/consumer.txt b/Documentation/power/regulator/consumer.txt
> index 81c0e2b49cd8..8afb236ca765 100644
> --- a/Documentation/power/regulator/consumer.txt
> +++ b/Documentation/power/regulator/consumer.txt
> @@ -143,8 +143,9 @@ This will cause the core to recalculate the total load on the regulator (based
>  on all its consumers) and change operating mode (if necessary and permitted)
>  to best match the current operating load.
>  
> -The load_uA value can be determined from the consumers datasheet. e.g.most
> -datasheets have tables showing the max current consumed in certain situations.
> +The load_uA value can be determined from the consumer's datasheet. e.g. most

Prefer:                                                               E.g.

otherwise,
Acked-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.

> +datasheets have tables showing the maximum current consumed in certain
> +situations.
>  
>  Most consumers will use indirect operating mode control since they have no
>  knowledge of the regulator or whether the regulator is shared with other


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/