From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Colin King <colin.king@canonical.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf jit: fix typo: "incalid" -> "invalid"
Date: Tue, 27 Jun 2017 11:54:41 -0300 [thread overview]
Message-ID: <20170627145441.GB16387@kernel.org> (raw)
In-Reply-To: <20170627124917.19151-1-colin.king@canonical.com>
Em Tue, Jun 27, 2017 at 01:49:17PM +0100, Colin King escreveu:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to typo in mlx4_dbg warnx warning message
Was this coccinele'd or otherwise automated? Would be nice to have this
described in the cset log, I'm replacing mlx4_dbg() with jvmti_close()
on this one, thanks,
- Arnaldo
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> tools/perf/jvmti/jvmti_agent.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/jvmti/jvmti_agent.c b/tools/perf/jvmti/jvmti_agent.c
> index e9651a9d670e..cf36de7ea255 100644
> --- a/tools/perf/jvmti/jvmti_agent.c
> +++ b/tools/perf/jvmti/jvmti_agent.c
> @@ -304,7 +304,7 @@ jvmti_close(void *agent)
> FILE *fp = agent;
>
> if (!fp) {
> - warnx("jvmti: incalid fd in close_agent");
> + warnx("jvmti: invalid fd in close_agent");
> return -1;
> }
>
> --
> 2.11.0
next prev parent reply other threads:[~2017-06-27 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 12:49 [PATCH] perf jit: fix typo: "incalid" -> "invalid" Colin King
2017-06-27 14:54 ` Arnaldo Carvalho de Melo [this message]
2017-06-27 14:56 ` Colin Ian King
2017-06-27 19:08 ` Arnaldo Carvalho de Melo
2017-07-01 8:49 ` [tip:perf/core] " tip-bot for Colin Ian King
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=20170627145441.GB16387@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.