linux-kernel - Re: [PATCH] Documentation: Fix minor typos in pinctrl.txt

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]

Date:	Tue, 15 Nov 2011 13:24:58 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Rajendra Nayak <rnayak@...com>
CC:	linus.walleij@...ricsson.com, linux-kernel@...r.kernel.org,
	linaro-dev@...ts.linaro.org
Subject: Re: [PATCH] Documentation: Fix minor typos in pinctrl.txt

On 11/14/2011 09:36 PM, Rajendra Nayak wrote:
> Fix some minor typos in the pinctrl documentation.
> 
> Signed-off-by: Rajendra Nayak <rnayak@...com>
> ---
>  Documentation/pinctrl.txt |   16 ++++++++--------
>  1 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
> index b04cb7d..c849a09 100644
> --- a/Documentation/pinctrl.txt
> +++ b/Documentation/pinctrl.txt
> @@ -91,7 +91,7 @@ int __init foo_probe(void)
>  Pins usually have fancier names than this. You can find these in the dataheet

fix typo:                                                               datasheet

>  for your chip. Notice that the core pinctrl.h file provides a fancy macro
>  called PINCTRL_PIN() to create the struct entries. As you can see I enumerated
> -the pins from 0 in the upper left corner to 63 in the lower right corner,
> +the pins from 0 in the lower left corner to 63 in the upper right corner,

fix run-on sentences:

   the pins from 0 in the lower left corner to 63 in the upper right corner.
   This enumeration was arbitrarily chosen; in practice you need to think

>  this enumeration was arbitrarily chosen, in practice you need to think
>  through your numbering system so that it matches the layout of registers
>  and such things in your driver, or the code may become complicated. You must


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/