From: David Brownell <david-b@pacbell.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org,
"Dominik D. Geyer" <dominik.geyer@gmx.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 4/6] docs: correct gpio.txt typos
Date: Tue, 8 Dec 2009 14:23:05 -0800 [thread overview]
Message-ID: <200912081423.05173.david-b@pacbell.net> (raw)
In-Reply-To: <12601530441131@xenotime.net>
On Sunday 06 December 2009, Randy Dunlap wrote:
> From: Dominik D. Geyer <dominik.geyer@gmx.de>
> Subject: correct gpio.txt typos
>
> Corrected sysfs gpio chip node name and fixed punctuation.
>
> Signed-off-by: Dominik D. Geyer <dominik.geyer@gmx.de>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: David Brownell <dbrownell@users.sourceforge.net>
Ack.
> ---
> Documentation/gpio.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- lnx-2632-rc6.orig/Documentation/gpio.txt
> +++ lnx-2632-rc6/Documentation/gpio.txt
> @@ -380,7 +380,7 @@ rare; use gpiochip_remove() when it is u
>
> Most often a gpio_chip is part of an instance-specific structure with state
> not exposed by the GPIO interfaces, such as addressing, power management,
> -and more. Chips such as codecs will have complex non-GPIO state,
> +and more. Chips such as codecs will have complex non-GPIO state.
>
> Any debugfs dump method should normally ignore signals which haven't been
> requested as GPIOs. They can use gpiochip_is_requested(), which returns
> @@ -531,7 +531,7 @@ and have the following read/write attrib
> This file exists only if the pin can be configured as an
> interrupt generating input pin.
>
> -GPIO controllers have paths like /sys/class/gpio/chipchip42/ (for the
> +GPIO controllers have paths like /sys/class/gpio/gpiochip42/ (for the
> controller implementing GPIOs starting at #42) and have the following
> read-only attributes:
>
>
>
> --
>
>
parent reply other threads:[~2009-12-08 22:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <12601530441131@xenotime.net>]
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=200912081423.05173.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dominik.geyer@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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®