From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Aditya Gupta <adityag@linux.ibm.com>
Cc: jolsa@kernel.org, irogers@google.com, namhyung@kernel.org,
linux-perf-users@vger.kernel.org, maddy@linux.ibm.com,
atrajeev@linux.vnet.ibm.com, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com
Subject: Re: [PATCH v6 1/4] perf check: introduce check subcommand
Date: Fri, 10 Nov 2023 11:31:56 -0300 [thread overview]
Message-ID: <ZU4+3HxUMg7hW52e@kernel.org> (raw)
In-Reply-To: <ZU493oMRpGgNBrQV@kernel.org>
Em Fri, Nov 10, 2023 at 11:27:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sat, Oct 21, 2023 at 08:35:23PM +0530, Aditya Gupta escreveu:
> > Acked-by: Namhyung Kim <namhyung@kernel.org>
> > Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
> Right after applying this first patch:
> [acme@quaco perf-tools-next]$ m
> make: Entering directory '/home/acme/git/perf-tools-next/tools/perf'
> builtin-check.c:53:56: error: expected ‘}’ before ‘;’ token
> 53 | FEATURE_SUPPORT("bpf_skeletons", HAVE_BPF_SKEL);
> | ^
> builtin-check.c:29:47: note: to match this ‘{’
> 29 | struct feature_support supported_features[] = {
> | ^
> make[3]: *** [/home/acme/git/perf-tools-next/tools/build/Makefile.build:106: /tmp/build/perf-tools-next/builtin-check.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[2]: *** [Makefile.perf:669: /tmp/build/perf-tools-next/perf-in.o] Error 2
> make[1]: *** [Makefile.perf:242: sub-make] Error 2
> make: *** [Makefile:113: install-bin] Error 2
> make: Leaving directory '/home/acme/git/perf-tools-next/tools/perf'
It was a simple error, please be more careful next time.
I'm testing the rest of the patchset now.
- Arnaldo
diff --git a/tools/perf/builtin-check.c b/tools/perf/builtin-check.c
index 1183983e4352798d..1502804780507b5d 100644
--- a/tools/perf/builtin-check.c
+++ b/tools/perf/builtin-check.c
@@ -50,7 +50,7 @@ struct feature_support supported_features[] = {
FEATURE_SUPPORT("zstd", HAVE_ZSTD_SUPPORT),
FEATURE_SUPPORT("libpfm4", HAVE_LIBPFM),
FEATURE_SUPPORT("libtraceevent", HAVE_LIBTRACEEVENT),
- FEATURE_SUPPORT("bpf_skeletons", HAVE_BPF_SKEL);
+ FEATURE_SUPPORT("bpf_skeletons", HAVE_BPF_SKEL),
/* this should remain at end, to know the array end */
FEATURE_SUPPORT(NULL, _)
next prev parent reply other threads:[~2023-11-10 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 15:05 [PATCH v6 0/4] Introduce perf check subcommand Aditya Gupta
2023-10-21 15:05 ` [PATCH v6 1/4] perf check: introduce " Aditya Gupta
2023-11-10 14:27 ` Arnaldo Carvalho de Melo
2023-11-10 14:31 ` Arnaldo Carvalho de Melo [this message]
2023-11-10 14:38 ` Arnaldo Carvalho de Melo
2023-11-10 22:46 ` Namhyung Kim
2023-11-16 7:12 ` Aditya Gupta
2023-11-16 7:06 ` Aditya Gupta
2023-11-16 6:52 ` Aditya Gupta
2023-10-21 15:05 ` [PATCH v6 2/4] perf version: update --build-options to use 'supported_features' array Aditya Gupta
2023-10-21 15:05 ` [PATCH v6 3/4] perf tests task_analyzer: use perf check for libtraceevent support Aditya Gupta
2023-10-21 15:05 ` [PATCH v6 4/4] tools/perf/tests: Update probe_vfs_getname.sh script to use perf check --feature Aditya Gupta
2023-11-07 3:42 ` [PATCH v6 0/4] Introduce perf check subcommand Aditya Gupta
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=ZU4+3HxUMg7hW52e@kernel.org \
--to=acme@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).