public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Soramichi AKIYAMA <akiyama@m.soramichi.jp>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com
Subject: Re: [PATCH] [Performance Events] Fix typo in tools/perf/evlist.c
Date: Tue, 10 Jan 2017 10:46:07 -0300	[thread overview]
Message-ID: <20170110134607.GD24073@kernel.org> (raw)
In-Reply-To: <20170110200006.e1f7a766b4faf1f107ae2e1b@m.soramichi.jp>

Em Tue, Jan 10, 2017 at 08:00:06PM +0900, Soramichi AKIYAMA escreveu:
> This patch fixes a typo: s/enable to/unable to/

Thanks, somehow it didn't apply cleanly, did it manually, added Fixes:
tag, ended up as:

commit c628c4d72895768624d0386b672992005c2561ac
Author: Soramichi Akiyama <akiyama@m.soramichi.jp>
Date:   Tue Jan 10 10:41:00 2017 -0300

    perf evlist: Fix typo in perf_evlist__start_workload()
    
    This patch fixes a typo: s/enable to/unable to/
    
    Signed-off-by: Soramichi AKIYAMA <akiyama@m.soramichi.jp>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Namhyung Kim <namhyung.kim@lge.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Fixes: bcf3145fbeb1 ("perf evlist: Enhance perf_evlist__start_workload()")
    Link: http://lkml.kernel.org/r/20170110200006.e1f7a766b4faf1f107ae2e1b@m.soramichi.jp
    [ Wasn't applying, fixed it up by hand, added Fixes: tag ]
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
index bdff42e3c75e..dc4df3d2660e 100644
--- a/tools/perf/util/evlist.c
+++ b/tools/perf/util/evlist.c
@@ -1801,7 +1801,7 @@ int perf_evlist__start_workload(struct perf_evlist *evlist)
 		 */
 		ret = write(evlist->workload.cork_fd, &bf, 1);
 		if (ret < 0)
-			perror("enable to write to pipe");
+			perror("unable to write to pipe");
 
 		close(evlist->workload.cork_fd);
 		return ret;
 
> Signed-off-by: Soramichi Akiyama <akiyama@m.soramichi.jp>
> ---
>  tools/perf/util/evlist.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
> index d92e020..23e6f33 100644
> --- a/tools/perf/util/evlist.c
> +++ b/tools/perf/util/evlist.c
> @@ -1797,7 +1797,7 @@ int perf_evlist__start_workload(struct perf_evlist *evlist)
>                  */
>                 ret = write(evlist->workload.cork_fd, &bf, 1);
>                 if (ret < 0)
> -                       perror("enable to write to pipe");
> +                       perror("unable to write to pipe");
>  
>                 close(evlist->workload.cork_fd);
>                 return ret;
> -- 
> 2.1.4

  reply	other threads:[~2017-01-10 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 11:00 [PATCH] [Performance Events] Fix typo in tools/perf/evlist.c Soramichi AKIYAMA
2017-01-10 13:46 ` Arnaldo Carvalho de Melo [this message]
2017-01-12  8:30 ` [tip:perf/core] perf evlist: Fix typo in perf_evlist__start_workload() tip-bot for Soramichi Akiyama

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=20170110134607.GD24073@kernel.org \
    --to=acme@kernel.org \
    --cc=akiyama@m.soramichi.jp \
    --cc=alexander.shishkin@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox