From: Ingo Molnar <mingo@kernel.org>
To: Yabin Cui <yabinc@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v5 0/3] perf/core: Check sample_type in sample data saving helper functions
Date: Tue, 19 Nov 2024 09:27:28 +0100 [thread overview]
Message-ID: <ZzxL8Od8CAEH4_Np@gmail.com> (raw)
In-Reply-To: <CALJ9ZPNkO=_OKPDwdSY9tJw+AETaAVC2m-1UcWScZ0TaFmHRkw@mail.gmail.com>
* Yabin Cui <yabinc@google.com> wrote:
> Hi, friendly ping again for review?
Sorry about the delay, this feel between the cracks. I've applied your
series to tip:perf/core, nice work and thanks a lot!
Ingo
prev parent reply other threads:[~2024-11-19 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 19:36 [PATCH v5 0/3] perf/core: Check sample_type in sample data saving helper functions Yabin Cui
2024-05-15 19:36 ` [PATCH v5 1/3] perf/core: Save raw sample data conditionally based on sample type Yabin Cui
2024-11-19 8:48 ` [tip: perf/core] " tip-bot2 for Yabin Cui
2024-05-15 19:36 ` [PATCH v5 2/3] perf/core: Check sample_type in perf_sample_save_callchain Yabin Cui
2024-11-19 8:48 ` [tip: perf/core] " tip-bot2 for Yabin Cui
2024-05-15 19:36 ` [PATCH v5 3/3] perf/core: Check sample_type in perf_sample_save_brstack Yabin Cui
2024-11-19 8:48 ` [tip: perf/core] " tip-bot2 for Yabin Cui
2024-05-22 16:26 ` [PATCH v5 0/3] perf/core: Check sample_type in sample data saving helper functions Namhyung Kim
2024-05-28 17:59 ` Yabin Cui
2024-06-11 20:33 ` Yabin Cui
2024-11-19 8:27 ` Ingo Molnar [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=ZzxL8Od8CAEH4_Np@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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=yabinc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.