From: Ian Rogers <irogers@google.com>
To: Riccardo Mancini <rickyman7@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 0/3] tools: add gettid to libc_compat.h
Date: Thu, 22 Jul 2021 16:31:40 -0700 [thread overview]
Message-ID: <CAP-5=fWxuGkJdFPNt7B=t3bc81jP8YWOUdyvfFcntStGqUxuag@mail.gmail.com> (raw)
In-Reply-To: <cover.1626966805.git.rickyman7@gmail.com>
On Thu, Jul 22, 2021 at 8:34 AM Riccardo Mancini <rickyman7@gmail.com> wrote:
>
> Hi Arnaldo,
>
> following our previous discussion on workqueue RFC patchset, I'm sending
> this patchet to add gettid to tools/include/tools/libc_compat.h.
> This new definition will replace existing uses and will be used by the
> workqueue code.
>
> Thanks,
> Riccardo
>
> Riccardo Mancini (3):
> tools libc_compat: add gettid
> perf jvmti: use gettid from libc_compat
> perf test: mmap-thread-lookup: use gettid
>
> tools/include/tools/libc_compat.h | 7 +++++++
> tools/perf/jvmti/jvmti_agent.c | 9 +--------
> tools/perf/tests/mmap-thread-lookup.c | 4 ++--
> 3 files changed, 10 insertions(+), 10 deletions(-)
All 3 patches look like great cleanup, thanks!
Acked-by: Ian Rogers <irogers@google.com>
Thanks,
Ian
prev parent reply other threads:[~2021-07-22 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 15:34 [PATCH 0/3] tools: add gettid to libc_compat.h Riccardo Mancini
2021-07-22 15:34 ` [PATCH 1/3] tools libc_compat: add gettid Riccardo Mancini
[not found] ` <202107260534.Q3Cd7MYm-lkp@intel.com>
2021-07-26 10:43 ` Riccardo Mancini
2021-07-22 15:34 ` [PATCH 2/3] perf jvmti: use gettid from libc_compat Riccardo Mancini
2021-07-22 15:34 ` [PATCH 3/3] perf test: mmap-thread-lookup: use gettid Riccardo Mancini
2021-07-22 23:31 ` Ian Rogers [this message]
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='CAP-5=fWxuGkJdFPNt7B=t3bc81jP8YWOUdyvfFcntStGqUxuag@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rickyman7@gmail.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).