From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: carsten.haitzler@foss.arm.com, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org, suzuki.poulose@arm.com,
mathieu.poirier@linaro.org, mike.leach@linaro.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v7 00/14] perf: test: Add trace data quality tests for CoreSight
Date: Sat, 13 Aug 2022 15:11:23 -0300 [thread overview]
Message-ID: <YvfpS+Lc/cI8BCg2@kernel.org> (raw)
In-Reply-To: <YvfpCnZ30tKFBfG+@kernel.org>
Em Sat, Aug 13, 2022 at 03:10:18PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sat, Aug 13, 2022 at 10:17:39PM +0800, Leo Yan escreveu:
> > On Fri, Aug 12, 2022 at 04:02:50PM -0300, Arnaldo Carvalho de Melo wrote:
> > So with fixing the merging conflict:
> >
> > Tested-by: Leo Yan <leo.yan@linaro.org>
> > Reviewed-by: Leo Yan <leo.yan@linaro.org>
>
> [PATCH v7 14/14] perf test: Add relevant documentation about CoreSight testing
> + Tested-by: Leo Yan <leo.yan@linaro.org> (✓ DKIM/linaro.org)
> + Reviewed-by: Leo Yan <leo.yan@linaro.org> (✓ DKIM/linaro.org)
> ---
> Total patches: 14
> ---
> NOTE: some trailers ignored due to from/email mismatches:
> ! Trailer: Link: https://lore.kernel.org/r/20220728145256.2985298-1-carsten.haitzler@foss.arm.com
> Msg From: Arnaldo Carvalho de Melo <acme@kernel.org>
> NOTE: Rerun with -S to apply them anyway
> ---
> Cover: ./v7_20220812_carsten_haitzler_perf_test_add_trace_data_quality_tests_for_coresight.cover
> Link: https://lore.kernel.org/r/20220812121641.336465-1-carsten.haitzler@foss.arm.com
> Base: not specified
> git am ./v7_20220812_carsten_haitzler_perf_test_add_trace_data_quality_tests_for_coresight.mbx
> ⬢[acme@toolbox perf]$ git am ./v7_20220812_carsten_haitzler_perf_test_add_trace_data_quality_tests_for_coresight.mbx
> Applying: perf test: Refactor shell tests allowing subdirs
> .git/rebase-apply/patch:56: trailing whitespace.
> /*
> warning: 1 line adds whitespace errors.
> tools/perf/tests/builtin-test-list.c:29: trailing whitespace.
> +/*
> ⬢[acme@toolbox perf]$
>
>
> Fixing...
After that:
⬢[acme@toolbox perf]$ git am ./v7_20220812_carsten_haitzler_perf_test_add_trace_data_quality_tests_for_coresight.mbx
Applying: perf test: Refactor shell tests allowing subdirs
Applying: perf test: Add CoreSight shell lib shared code for future tests
Applying: perf test: Add build infra for perf test tools for CoreSight tests
error: patch failed: tools/perf/Makefile.perf:1015
error: tools/perf/Makefile.perf: patch does not apply
.git/rebase-apply/patch:109: new blank line at EOF.
+
Patch failed at 0003 perf test: Add build infra for perf test tools for CoreSight tests
hint: Use 'git am --show-current-patch=diff' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
⬢[acme@toolbox perf]$
Fixing...
next prev parent reply other threads:[~2022-08-13 18:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 12:16 [PATCH v7 00/14] perf: test: Add trace data quality tests for CoreSight carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 01/14] perf test: Refactor shell tests allowing subdirs carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 02/14] perf test: Add CoreSight shell lib shared code for future tests carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 03/14] perf test: Add build infra for perf test tools for CoreSight tests carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 04/14] perf test: Add asm pureloop test tool carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 05/14] perf test: Add asm pureloop test shell script carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 06/14] perf test: Add git ignore for perf data generated by the CoreSight tests carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 07/14] perf test: Add memcpy thread test tool carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 08/14] perf test: Add memcpy thread test shell script carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 09/14] perf test: Add thread loop test tool carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 10/14] perf test: Add thread loop test shell scripts carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 11/14] perf test: Add unroll thread test tool carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 12/14] perf test: Add unroll thread test shell script carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 13/14] perf test: Add git ignore for tmp and output files of CoreSight tests carsten.haitzler
2022-08-12 12:16 ` [PATCH v7 14/14] perf test: Add relevant documentation about CoreSight testing carsten.haitzler
2022-08-12 18:51 ` [PATCH v7 00/14] perf: test: Add trace data quality tests for CoreSight Arnaldo Carvalho de Melo
2022-08-12 18:53 ` Arnaldo Carvalho de Melo
2022-08-12 18:55 ` Arnaldo Carvalho de Melo
2022-08-12 19:00 ` Arnaldo Carvalho de Melo
2022-08-15 8:00 ` Carsten Haitzler
2022-08-15 8:02 ` Carsten Haitzler
2022-08-12 19:02 ` Arnaldo Carvalho de Melo
2022-08-13 14:17 ` Leo Yan
2022-08-13 18:10 ` Arnaldo Carvalho de Melo
2022-08-13 18:11 ` Arnaldo Carvalho de Melo [this message]
2022-08-13 18:14 ` Arnaldo Carvalho de Melo
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=YvfpS+Lc/cI8BCg2@kernel.org \
--to=acme@kernel.org \
--cc=carsten.haitzler@foss.arm.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).