From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Aditya Gupta <adityag@linux.ibm.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Namhyung Kim <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 v14 3/7] perf version: Update --build-options to use 'supported_features' array
Date: Wed, 4 Sep 2024 16:15:01 -0300 [thread overview]
Message-ID: <ZtixtQiG20UFWEkd@x1> (raw)
In-Reply-To: <b48b172e-d465-4dc5-abd6-7da7a47e5c9c@linux.ibm.com>
On Thu, Sep 05, 2024 at 12:36:21AM +0530, Aditya Gupta wrote:
> Hi Arnaldo,
>
> On 04/09/24 18:35, Arnaldo Carvalho de Melo wrote:
>
> > On Wed, Sep 04, 2024 at 11:48:32AM +0530, Aditya Gupta wrote:
> > > Now that the feature list has been duplicated in a global
> > > 'supported_features' array, use that array instead of manually checking
> > > status of built-in features.
> > >
> > > This helps in being consistent with commands such as 'perf check feature',
> > > so commands can use the same array, and any new feature can be added at
> > > one place, in the 'supported_features' array
> > So I tested and applied the first two patches, but it is failing for
> > this 3rd, please rebase from what is in the tmp.perf-tools-next branch
> > at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
>
> Thank you !
>
> I have rebased the patches in v15.
>
> Patch #1 & #2, are same as already applied in tmp.perf-tools-next branch, so
> they can be ignored or even if applied git am should ignore them.
I dit it with:
[acme@toolbox perf-tools-next]$ b4 am -P3-7 -ctsl --cc-trailers 20240904190132.415212-1-adityag@linux.ibm.com
Grabbing thread from lore.kernel.org/all/20240904190132.415212-1-adityag@linux.ibm.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Nothing matching that query.
Analyzing 8 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v15 3/7] perf version: Update --build-options to use 'supported_features' array
+ Link: https://lore.kernel.org/r/20240904190132.415212-4-adityag@linux.ibm.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
✓ [PATCH v15 4/7] tools/perf/tests: Update test_task_analyzer.sh to use perf check feature
+ Link: https://lore.kernel.org/r/20240904190132.415212-5-adityag@linux.ibm.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
✓ [PATCH v15 5/7] tools/perf/tests: Update probe_vfs_getname.sh script to use perf check feature
+ Link: https://lore.kernel.org/r/20240904190132.415212-6-adityag@linux.ibm.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
✓ [PATCH v15 6/7] perf: Fix inconsistencies in feature names
+ Link: https://lore.kernel.org/r/20240904190132.415212-7-adityag@linux.ibm.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
✓ [PATCH v15 7/7] perf: Add more features to supported_features list
+ Link: https://lore.kernel.org/r/20240904190132.415212-8-adityag@linux.ibm.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
✓ Signed: DKIM/ibm.com (From: adityag@linux.ibm.com)
---
Total patches: 5 (cherrypicked: 3-7)
---
Cover: ./v15_20240905_adityag_introduce_perf_check_subcommand.cover
Link: https://lore.kernel.org/r/20240904190132.415212-1-adityag@linux.ibm.com
Base: not specified
git am ./v15_20240905_adityag_introduce_perf_check_subcommand.mbx
⬢[acme@toolbox perf-tools-next]$
⬢[acme@toolbox perf-tools-next]$ git am ./v15_20240905_adityag_introduce_perf_check_subcommand.mbx
Applying: perf version: Update --build-options to use 'supported_features' array
Applying: tools/perf/tests: Update test_task_analyzer.sh to use perf check feature
Applying: tools/perf/tests: Update probe_vfs_getname.sh script to use perf check feature
Applying: perf: Fix inconsistencies in feature names
Applying: perf: Add more features to supported_features list
⬢[acme@toolbox perf-tools-next]$
Now test building it one after the other and then the container builds,
eventually will flow to perf-tools-next.
Thanks for persisting and collaborating!
- Arnaldo
next prev parent reply other threads:[~2024-09-04 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:18 [PATCH v14 0/7] Introduce perf check subcommand Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 1/7] tools/lib/subcmd: Don't free the usage string Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 2/7] perf check: Introduce 'check' subcommand Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 3/7] perf version: Update --build-options to use 'supported_features' array Aditya Gupta
2024-09-04 13:05 ` Arnaldo Carvalho de Melo
2024-09-04 19:06 ` Aditya Gupta
2024-09-04 19:15 ` Arnaldo Carvalho de Melo [this message]
2024-09-04 6:18 ` [PATCH v14 4/7] tools/perf/tests: Update test_task_analyzer.sh to use perf check feature Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 5/7] tools/perf/tests: Update probe_vfs_getname.sh script " Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 6/7] perf: Fix inconsistencies in feature names Aditya Gupta
2024-09-04 6:18 ` [PATCH v14 7/7] perf: Add more features to supported_features list 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=ZtixtQiG20UFWEkd@x1 \
--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).