public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Proofread documentation
Date: Mon, 25 Aug 2014 09:58:14 -0700	[thread overview]
Message-ID: <53FB6B26.3030906@infradead.org> (raw)
In-Reply-To: <1408956471-16579-1-git-send-email-geert+renesas@glider.be>

On 08/25/14 01:47, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.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@infradead.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

  reply	other threads:[~2014-08-25 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  8:47 [PATCH] regulator: Proofread documentation Geert Uytterhoeven
2014-08-25 16:58 ` Randy Dunlap [this message]
2014-08-25 17:10   ` Geert Uytterhoeven
2014-08-25 17:14     ` Randy Dunlap
2014-08-27 21:05 ` Mark Brown

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=53FB6B26.3030906@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=broonie@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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