mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linus.walleij@stericsson.com, linux-kernel@vger.kernel.org,
	linaro-dev@lists.linaro.org
Subject: Re: [PATCH] Documentation: Fix minor typos in pinctrl.txt
Date: Tue, 15 Nov 2011 13:24:58 -0800	[thread overview]
Message-ID: <4EC2D8AA.6080701@xenotime.net> (raw)
In-Reply-To: <1321335378-29064-1-git-send-email-rnayak@ti.com>

On 11/14/2011 09:36 PM, Rajendra Nayak wrote:
> Fix some minor typos in the pinctrl documentation.
> 
> Signed-off-by: Rajendra Nayak <rnayak@ti.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 ***

  reply	other threads:[~2011-11-15 21:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  5:36 Rajendra Nayak
2011-11-15 21:24 ` Randy Dunlap [this message]
2011-11-17  8:46 ` Linus Walleij

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=4EC2D8AA.6080701@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rnayak@ti.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®