mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, trivial@kernel.org
Subject: Re: [PATCH] [linux-next] irq: Fix typo in tracepoint.xml
Date: Tue, 5 Jul 2016 17:29:33 -0400	[thread overview]
Message-ID: <20160705172933.53b626f5@gandalf.local.home> (raw)
In-Reply-To: <20160629084425.7503-1-standby24x7@gmail.com>

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

      reply	other threads:[~2016-07-05 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  8:44 Masanari Iida
2016-07-05 21:29 ` Steven Rostedt [this message]

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=20160705172933.53b626f5@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=standby24x7@gmail.com \
    --cc=trivial@kernel.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®