From: Ze Gao <zegao2021@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, Ze Gao <zegao@tencent.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 0/4] perf sched: Fix task state report
Date: Wed, 24 Jan 2024 10:08:30 +0800 [thread overview]
Message-ID: <CAD8CoPBpkeSFcFv3Fs+0TkafmUY4x3NdtfqPfqei2f246xFYZA@mail.gmail.com> (raw)
In-Reply-To: <170605662743.1691877.1586103440745721732.b4-ty@kernel.org>
On Wed, Jan 24, 2024 at 8:38 AM Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Mon, 22 Jan 2024 02:08:55 -0500, Ze Gao wrote:
> > No functional changes introduced in v2, just got v1 rebased onto
> > the tip of perf-tools-next for a clean apply.
> >
>
> Applied to perf-tools-next except for the last refactoring one.
> I'll test it separately.
Awesome!
Thanks,
-- Ze
> Best regards,
> --
> Namhyung Kim <namhyung@kernel.org>
prev parent reply other threads:[~2024-01-24 2:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 7:08 [PATCH v2 0/4] perf sched: Fix task state report Ze Gao
2024-01-22 7:08 ` [PATCH v2 1/4] perf sched: Sync state char array with the kernel Ze Gao
2024-01-22 7:08 ` [PATCH v2 2/4] perf util: Add helpers to parse task state string from libtraceevent Ze Gao
2024-01-22 7:08 ` [PATCH v2 3/4] perf util: Add evsel__taskstate() to parse the task state info instead Ze Gao
2024-01-22 7:08 ` [PATCH v2 4/4] perf sched: Commit to evsel__taskstate() to parse task state info Ze Gao
2024-01-23 0:38 ` Namhyung Kim
2024-01-23 2:09 ` Ze Gao
2024-01-23 2:24 ` Ze Gao
2024-01-24 0:17 ` Namhyung Kim
2024-01-23 7:02 ` [PATCH] perf evsel: Rename get_states() to parse_task_states() and make it public Ze Gao
2024-02-02 20:57 ` Namhyung Kim
2024-02-04 2:03 ` Ze Gao
2024-01-24 0:38 ` [PATCH v2 0/4] perf sched: Fix task state report Namhyung Kim
2024-01-24 2:08 ` Ze Gao [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=CAD8CoPBpkeSFcFv3Fs+0TkafmUY4x3NdtfqPfqei2f246xFYZA@mail.gmail.com \
--to=zegao2021@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--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=rostedt@goodmis.org \
--cc=zegao@tencent.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).