All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Colin Ian King <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	hpa@zytor.com, namhyung@kernel.org, peterz@infradead.org,
	acme@redhat.com, colin.king@canonical.com, mojha@codeaurora.org,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@kernel.org
Subject: [tip:perf/core] perf test: Fix spelling mistake "leadking" -> "leaking"
Date: Sat, 18 May 2019 01:47:03 -0700	[thread overview]
Message-ID: <tip-1455ea2391be5a5bf0a53258af94fa2abbd73cca@git.kernel.org> (raw)
In-Reply-To: <20190417105539.5902-1-colin.king@canonical.com>

Commit-ID:  1455ea2391be5a5bf0a53258af94fa2abbd73cca
Gitweb:     https://git.kernel.org/tip/1455ea2391be5a5bf0a53258af94fa2abbd73cca
Author:     Colin Ian King <colin.king@canonical.com>
AuthorDate: Wed, 17 Apr 2019 11:55:39 +0100
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed, 15 May 2019 16:36:46 -0300

perf test: Fix spelling mistake "leadking" -> "leaking"

There are a couple of spelling mistakes in test assert messages. Fix them.

Signed-off-by: Colin King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: kernel-janitors@vger.kernel.org
Link: http://lkml.kernel.org/r/20190417105539.5902-1-colin.king@canonical.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/tests/dso-data.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/perf/tests/dso-data.c b/tools/perf/tests/dso-data.c
index 7f6c52021e41..946ab4b63acd 100644
--- a/tools/perf/tests/dso-data.c
+++ b/tools/perf/tests/dso-data.c
@@ -304,7 +304,7 @@ int test__dso_data_cache(struct test *test __maybe_unused, int subtest __maybe_u
 	/* Make sure we did not leak any file descriptor. */
 	nr_end = open_files_cnt();
 	pr_debug("nr start %ld, nr stop %ld\n", nr, nr_end);
-	TEST_ASSERT_VAL("failed leadking files", nr == nr_end);
+	TEST_ASSERT_VAL("failed leaking files", nr == nr_end);
 	return 0;
 }
 
@@ -380,6 +380,6 @@ int test__dso_data_reopen(struct test *test __maybe_unused, int subtest __maybe_
 	/* Make sure we did not leak any file descriptor. */
 	nr_end = open_files_cnt();
 	pr_debug("nr start %ld, nr stop %ld\n", nr, nr_end);
-	TEST_ASSERT_VAL("failed leadking files", nr == nr_end);
+	TEST_ASSERT_VAL("failed leaking files", nr == nr_end);
 	return 0;
 }

  parent reply	other threads:[~2019-05-18  8:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 10:31 [PATCH] perf test: fix spelling mistake "sythesizing" -> "synthesizing" Colin King
2019-04-17 10:55 ` [PATCH] perf test: fix spelling mistake "leadking" -> "leaking" Colin King
2019-04-17 10:55   ` Colin King
2019-04-17 11:07   ` Mukesh Ojha
2019-04-17 11:19     ` Mukesh Ojha
2019-04-17 11:09     ` Colin Ian King
2019-04-17 11:09       ` Colin Ian King
2019-04-17 17:37     ` Arnaldo Carvalho de Melo
2019-04-17 17:37       ` Arnaldo Carvalho de Melo
2019-05-18  8:47   ` tip-bot for Colin Ian King [this message]
2019-09-11 15:21 ` [PATCH] perf test: fix spelling mistake "allos" -> "allocate" Colin King
2019-09-11 15:21   ` Colin King
2019-09-17  7:42   ` Mukesh Ojha
2019-09-17  7:54     ` Mukesh Ojha
2019-09-18 23:09     ` Arnaldo Carvalho de Melo
2019-09-18 23:09       ` Arnaldo Carvalho de Melo
2019-09-20 16:20   ` [tip: perf/urgent] perf test: Fix " tip-bot2 for Colin Ian King
2019-09-20 16:20     ` tip-bot2 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=tip-1455ea2391be5a5bf0a53258af94fa2abbd73cca@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=colin.king@canonical.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mojha@codeaurora.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.