From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ian Rogers <irogers@google.com>,
linux-kernel-next@vger.kernel.org,
linux-perf-users@vger.kernel.org, hca@linux.ibm.com,
egorenar@linux.ibm.com, gor@linux.ibm.com, svens@linux.ibm.com,
sumanthk@linux.ibm.com
Subject: Re: PING Re: [PATCH] tools/perf: Fix perf tool build error in util/pfm.c
Date: Wed, 15 Feb 2023 13:26:18 -0300 [thread overview]
Message-ID: <Y+0Hqgb4fFTx9XlX@kernel.org> (raw)
In-Reply-To: <283ace48-0e69-08a4-cfd2-7bee5779c45c@linux.ibm.com>
Em Wed, Feb 15, 2023 at 03:17:44PM +0100, Thomas Richter escreveu:
> Friendly ping, is this already in linux-next?
To answer that, next time, please:
$ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
$ git checkout -b linux-next-master linux-next/master
$ git log -10 --no-merges --oneline tools/perf
8f46f36d81a6b4f5 mm: discard __GFP_ATOMIC
14292a4ae1a37a7c perf bpf: Avoid build breakage with libbpf < 0.8.0 + LIBBPF_DYNAMIC=1
f00eccb447762c99 perf build: Fix build error when NO_LIBBPF=1
213b760fbc69f2d6 perf tools: Don't install libtraceevent plugins as its not anymore in the kernel sources
dce088ab0d51ae3b perf kmem: Support field "node" in evsel__process_alloc_event() coping with recent tracepoint restructuring
b3719108ae60169e perf kmem: Support legacy tracepoints
d891f2b724b39a2a perf build: Properly guard libbpf includes
6f9aba7f0d74e8dd perf tests bpf prologue: Fix bpf-script-test-prologue test compile issue with clang
481028dbf1daa280 (tag: perf-tools-fixes-for-v6.2-1-2023-01-06, tag: perf-tools-fixes-for-v6.1-1-2023-01-06) perf tools: Fix build on uClibc systems by adding missing sys/types.h include
54b353a20c7e8be9 perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match non BPF mode
$
So it isn't there, then:
⬢[acme@toolbox perf]$ git log --oneline -5
91621be65d6812cd (HEAD -> perf/core) perf record: Fix segfault with --overwrite and --max-size
37f322cd58d81a9d (quaco/perf/core, acme/tmp.perf/core) perf stat: Avoid merging/aggregating metric counts twice
6a5558f1166473f7 (seventh/perf/core, acme/perf/core) perf tools: Fix perf tool build error in util/pfm.c
ffd1240e8f081426 perf tools: Fix auto-complete on aarch64
1bece1351c653c3d perf lock contention: Support old rw_semaphore type
⬢[acme@toolbox perf]$
It is in my perf/core branch for some time, so should've been in
linux-next by now:
⬢[acme@toolbox perf]$ git show --pretty=fuller acme/perf/core | head
commit 6a5558f1166473f741de33c32ffb161d7f7732cb
Author: Thomas Richter <tmricht@linux.ibm.com>
AuthorDate: Tue Feb 7 15:04:47 2023 +0100
Commit: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Wed Feb 8 11:07:47 2023 -0300
perf tools: Fix perf tool build error in util/pfm.c
I have downloaded linux-next and build the perf tool using
⬢[acme@toolbox perf]$
In such cases please CC the linux-next maintainer:
Stephen, can you please merge acme/perf/core into linux-next?
- Arnaldo
next prev parent reply other threads:[~2023-02-15 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:04 [PATCH] tools/perf: Fix perf tool build error in util/pfm.c Thomas Richter
2023-02-07 15:02 ` Arnaldo Carvalho de Melo
2023-02-08 5:58 ` Ian Rogers
2023-02-08 13:40 ` Arnaldo Carvalho de Melo
2023-02-08 13:44 ` Arnaldo Carvalho de Melo
2023-02-08 14:07 ` Arnaldo Carvalho de Melo
2023-02-15 14:17 ` PING " Thomas Richter
2023-02-15 16:26 ` Arnaldo Carvalho de Melo [this message]
2023-02-15 20:28 ` Stephen Rothwell
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=Y+0Hqgb4fFTx9XlX@kernel.org \
--to=acme@kernel.org \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=linux-kernel-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tmricht@linux.ibm.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).