From: Doug Smythies <dsmythies@telus.net>
To: Jinzhou Su <Jinzhou.Su@amd.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Linux PM list <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"Huang, Ray" <ray.huang@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
todd.e.brandt@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
deepak.sharma@amd.com, alexander.deucher@amd.com,
xiaojian.du@amd.com, perry.yuan@amd.com, li.meng@amd.com,
dsmythies <dsmythies@telus.net>
Subject: Re: [PATCH 2/3] tools/power/x86/intel_pstate_tracer: make tracer as a module
Date: Wed, 23 Feb 2022 07:19:08 -0800 [thread overview]
Message-ID: <CAAYoRsWn_gjuBdS3vbo6ZxAXKur6YhXKTkZKpQY+k6hogcibUA@mail.gmail.com> (raw)
In-Reply-To: <20220223100350.3523826-3-Jinzhou.Su@amd.com>
On Wed, Feb 23, 2022 at 2:04 AM Jinzhou Su <Jinzhou.Su@amd.com> wrote:
>
> Make intel_pstate_tracer as a module. Other trace event can import
> this module to analyze their trace data.
>
> Signed-off-by: Jinzhou Su <Jinzhou.Su@amd.com>
HI Joe,
I have been using this version (well, with just 2 variable name changes,
which I see you changed back) since you sent it (off-list) on Feb 8th.
Acked-by: Doug Smythies <dsmythies@telus.net>
next prev parent reply other threads:[~2022-02-23 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:03 [PATCH 0/3] Add tracer tool for AMD P-State driver Jinzhou Su
2022-02-23 10:03 ` [PATCH 1/3] cpufreq: amd-pstate: Add more tracepoint for AMD P-State module Jinzhou Su
2022-03-01 15:26 ` Rafael J. Wysocki
2022-03-01 16:05 ` Deucher, Alexander
2022-03-01 16:07 ` Rafael J. Wysocki
2022-03-02 9:09 ` Huang Rui
2022-03-02 9:53 ` Su, Jinzhou (Joe)
2022-02-23 10:03 ` [PATCH 2/3] tools/power/x86/intel_pstate_tracer: make tracer as a module Jinzhou Su
2022-02-23 15:19 ` Doug Smythies [this message]
2022-02-23 10:03 ` [PATCH 3/3] tools/power/x86/amd_pstate_tracer: Add tracer tool for AMD P-state Jinzhou Su
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=CAAYoRsWn_gjuBdS3vbo6ZxAXKur6YhXKTkZKpQY+k6hogcibUA@mail.gmail.com \
--to=dsmythies@telus.net \
--cc=Jinzhou.Su@amd.com \
--cc=alexander.deucher@amd.com \
--cc=deepak.sharma@amd.com \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=ray.huang@amd.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=todd.e.brandt@linux.intel.com \
--cc=viresh.kumar@linaro.org \
--cc=xiaojian.du@amd.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).