2024-02-26 11:33:22

by Colin Ian King

Subject: [PATCH][next] perf test: Fix spelling mistake "curent" -> "current"

There is a spelling mistake in a pr_debug message. Fix it.

Signed-off-by: Colin Ian King <[email protected]>
---
tools/perf/tests/symbols.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/perf/tests/symbols.c b/tools/perf/tests/symbols.c
index 2fed6d67f50f..d208105919ed 100644
--- a/tools/perf/tests/symbols.c
+++ b/tools/perf/tests/symbols.c
@@ -85,7 +85,7 @@ static int create_map(struct test_info *ti, char *filename, struct map **map_p)
*map_p = find_module_map(ti->machine, dso);
dso__put(dso);
if (!*map_p) {
- pr_debug("Failed to find map for curent kernel module %s",
+ pr_debug("Failed to find map for current kernel module %s",
filename);
return TEST_FAIL;
}
--
2.39.2

2024-02-26 12:07:36

by Adrian Hunter

Subject: Re: [PATCH][next] perf test: Fix spelling mistake "curent" -> "current"

On 26/02/24 12:53, Colin Ian King wrote:
> There is a spelling mistake in a pr_debug message. Fix it.
>
> Signed-off-by: Colin Ian King <[email protected]>

Reviewed-by: Adrian Hunter <[email protected]>

> ---
> tools/perf/tests/symbols.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/symbols.c b/tools/perf/tests/symbols.c
> index 2fed6d67f50f..d208105919ed 100644
> --- a/tools/perf/tests/symbols.c
> +++ b/tools/perf/tests/symbols.c
> @@ -85,7 +85,7 @@ static int create_map(struct test_info *ti, char *filename, struct map **map_p)
> *map_p = find_module_map(ti->machine, dso);
> dso__put(dso);
> if (!*map_p) {
> - pr_debug("Failed to find map for curent kernel module %s",
> + pr_debug("Failed to find map for current kernel module %s",
> filename);
> return TEST_FAIL;
> }

2024-02-27 18:01:42

by Namhyung Kim

Subject: Re: [PATCH][next] perf test: Fix spelling mistake "curent" -> "current"

On Mon, 26 Feb 2024 10:53:26 +0000, Colin Ian King wrote:
> There is a spelling mistake in a pr_debug message. Fix it.
>
>

Applied to perf-tools-next, thanks!

Best regards,
--
Namhyung Kim <[email protected]>