From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Tingwei Zhang <tingweiz@codeaurora.org>,
Tingwei Zhang <tingwei@codeaurora.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
tsoni@codeaurora.org,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Mao Jinlong <jinlmao@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v3 0/6] tracing: export event trace and trace_marker
Date: Fri, 18 Sep 2020 17:26:38 +0300 [thread overview]
Message-ID: <87wo0rw481.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200914232729.GB20431@codeaurora.org>
Tingwei Zhang <tingweiz@codeaurora.org> writes:
> Hi Alexander, Maxime, Aleandre,
>
> May I know your comments for this patch set?
Everything except the last patch is
Reviewed-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
After that one is resolved either I can pick it up or Stephen. Either
way is fine with me.
Regards,
--
Alex
next prev parent reply other threads:[~2020-09-18 14:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 0:17 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 3/6] tracing: add trace_export support for event trace Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang
2020-09-03 0:17 ` [PATCH v3 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang
2020-09-18 12:45 ` Alexander Shishkin
2020-09-23 4:39 ` Tingwei Zhang
2020-09-14 23:27 ` [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-09-18 14:26 ` Alexander Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-13 1:45 Tingwei Zhang
2020-09-01 6:37 ` Tingwei Zhang
2020-09-01 17:05 ` Mathieu Poirier
2020-09-01 23:25 ` Tingwei Zhang
2020-09-01 23:28 ` Tingwei Zhang
2020-09-14 22:43 ` Steven Rostedt
2020-09-14 23:24 ` Tingwei Zhang
2020-08-11 3:57 Tingwei Zhang
2020-08-12 16:49 ` Mathieu Poirier
2020-08-13 1:47 ` Tingwei Zhang
2020-07-28 1:33 Tingwei Zhang
2020-08-11 3:04 ` Tingwei Zhang
2020-08-11 3:19 ` Steven Rostedt
[not found] ` <20200811034946.GA9338@codeaurora.org>
[not found] ` <20200811000333.5d24b16f@oasis.local.home>
2020-08-11 6:45 ` Tingwei Zhang
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=87wo0rw481.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@st.com \
--cc=jinlmao@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--cc=tingwei@codeaurora.org \
--cc=tingweiz@codeaurora.org \
--cc=tsoni@codeaurora.org \
/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