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

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

[Masanari Iida]

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@gmail.com>
---
 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.
  */
-- 
2.9.0.137.gcf4c2cf

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

[Steven Rostedt]

On Wed, 29 Jun 2016 17:44:25 +0900
Masanari Iida <standby24x7@gmail.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@gmail.com>

Acked-by: Steven Rostedt <rostedt@goodmis.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.
>   */