linux-kernel - Re: [PATCH 4/6] docs: correct gpio.txt typos

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>] [day] [month] [year] [list]

Message-Id: <200912081423.05173.david-b@pacbell.net>
Date:	Tue, 8 Dec 2009 14:23:05 -0800
From:	David Brownell <david-b@...bell.net>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	linux-kernel@...r.kernel.org,
	"Dominik D. Geyer" <dominik.geyer@....de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 4/6] docs: correct gpio.txt typos

On Sunday 06 December 2009, Randy Dunlap wrote:
> From: Dominik D. Geyer <dominik.geyer@....de>
> Subject: correct gpio.txt typos
> 
> Corrected sysfs gpio chip node name and fixed punctuation.
> 
> Signed-off-by: Dominik D. Geyer <dominik.geyer@....de>
> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> Cc: David Brownell <dbrownell@...rs.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:
>  
> 
> 
> -- 
> 
> 


--
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/