linux-kernel - Re: [PATCH] [linux-next] irq: Fix typo in tracepoint.xml

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: <20160705172933.53b626f5@gandalf.local.home>
Date:	Tue, 5 Jul 2016 17:29:33 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Masanari Iida <standby24x7@...il.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com, trivial@...nel.org
Subject: Re: [PATCH] [linux-next] irq: Fix typo in tracepoint.xml

On Wed, 29 Jun 2016 17:44:25 +0900
Masanari Iida <standby24x7@...il.com> wrote:

> This patch fix a spelling typo found in DocBook/tracepoint.xml.
> It is because the file was created from comments in source,
> so I have to fix the typo in include/trace/events/irq.h
> 
> Signed-off-by: Masanari Iida <standby24x7@...il.com>

Acked-by: Steven Rostedt <rostedt@...dmis.org>

I'm assuming that this will go through the trivial tree?

-- Steve

> ---
>  include/trace/events/irq.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/trace/events/irq.h b/include/trace/events/irq.h
> index f95f25e786ef..1c41b74581f7 100644
> --- a/include/trace/events/irq.h
> +++ b/include/trace/events/irq.h
> @@ -75,7 +75,7 @@ TRACE_EVENT(irq_handler_entry,
>   * @ret: return value
>   *
>   * If the @ret value is set to IRQ_HANDLED, then we know that the corresponding
> - * @action->handler scuccessully handled this irq. Otherwise, the irq might be
> + * @action->handler successfully handled this irq. Otherwise, the irq might be
>   * a shared irq line, or the irq was not handled successfully. Can be used in
>   * conjunction with the irq_handler_entry to understand irq handler latencies.
>   */