linux-kernel - Re: [PATCH] Doc: gpio: Fix typos in Documentation/gpio

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

Message-ID: <564A0513.4090906@infradead.org>
Date:	Mon, 16 Nov 2015 08:32:19 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Masanari Iida <standby24x7@...il.com>,
	linux-kernel@...r.kernel.org, corbet@....net,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] Doc: gpio: Fix typos in Documentation/gpio

On 11/16/15 03:00, Masanari Iida wrote:
> This patch fix some spelling typos found in Documentation/gpio.
> 
> Signed-off-by: Masanari Iida <standby24x7@...il.com>
> ---
>  Documentation/gpio/consumer.txt        | 4 ++--
>  Documentation/gpio/driver.txt          | 6 +++---
>  Documentation/gpio/drivers-on-gpio.txt | 6 +++---
>  3 files changed, 8 insertions(+), 8 deletions(-)


> diff --git a/Documentation/gpio/driver.txt b/Documentation/gpio/driver.txt
> index 12a6194..bbeec41 100644
> --- a/Documentation/gpio/driver.txt
> +++ b/Documentation/gpio/driver.txt
> @@ -113,8 +113,8 @@ GPIO irqchips usually fall in one of two categories:
>    it will be threaded IRQ handler on -RT and hard IRQ handler on non-RT
>    (for example, see [3]).
>    Know W/A: The generic_handle_irq() is expected to be called with IRQ disabled,

     Known

and I really would like to see all "W/A" changed to "workaround".
W/A is not a well known abbreviation.

As for the patch changes:
Acked-by: Randy Dunlap <rdunlap@...radead.org>

Thanks.


> -  so IRQ core will complain if it will be called from IRQ handler wich is forced
> -  thread. The "fake?" raw lock can be used to W/A this problem:
> +  so IRQ core will complain if it will be called from IRQ handler which is
> +  forced thread. The "fake?" raw lock can be used to W/A this problem:
>  
>  	raw_spinlock_t wa_lock;
>  	static irqreturn_t omap_gpio_irq_handler(int irq, void *gpiobank)

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