linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tingwei Zhang <tingweiz@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Tingwei Zhang <tingwei@codeaurora.org>,
	Ingo Molnar <mingo@redhat.com>,
	tsoni@codeaurora.org,
	Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
	Mao Jinlong <jinlmao@codeaurora.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] tracing: export event trace and trace_marker
Date: Tue, 11 Aug 2020 14:45:29 +0800	[thread overview]
Message-ID: <20200811064529.GA4253@codeaurora.org> (raw)
In-Reply-To: <20200811000333.5d24b16f@oasis.local.home>

On Tue, Aug 11, 2020 at 12:03:33PM +0800, Steven Rostedt wrote:
> On Tue, 11 Aug 2020 11:49:46 +0800
> Tingwei Zhang <tingweiz@codeaurora.org> wrote:
> 
> > On Tue, Aug 11, 2020 at 11:19:54AM +0800, Steven Rostedt wrote:
> > > On Tue, 11 Aug 2020 11:04:18 +0800
> > > Tingwei Zhang <tingweiz@codeaurora.org> wrote:
> > >   
> > > > Thanks for your comments, Steven.  I've addressed all your comments
> in  
> > > v3.  
> > > > Do you have more comments on v3? Is there anything I need to do to
> merge
> > > > this series to Linux Kernel?  
> > > 
> > > I gave my Reviewed-by tag on each of the patches that touch my tree.
> It
> > > should go in via whoever maintains the drivers/hwtracing tree. Is that
> > > Greg KH?  
> > I thought it will go to tracing tree since majority of the changes are
> in
> > kernel/trace.
> > 
> > Maintainers of drviers/hwtracing are Mathieu and Suzuki. I'll add them
> > into review list.
> >
> 
> As I didn't have reviews or acks from them. I couldn't take the code.
> When touching two subsystems, it usually requires one of the subsystem
> maintainers to ack the changes to their subsystem, so that the other
> subsystem maintainer can take the rest of the code through their tree.
> 
> And it usually goes through the tree that has the interface that is
> changing.  That is, the changes to tracing was the infrastructure
> needed for the changes in the hwtrace subsystem. And I don't test that
> subsystem, so I wouldn't really be able to test this code.
> 
Thanks a lot for detail clarification, Steven.

Thanks,
Tingwei

> -- Steve

  parent reply	other threads:[~2020-08-11  6:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  1:33 [PATCH v3 0/6] tracing: export event trace and trace_marker Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 1/6] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 2/6] tracing: add flag to control different traces Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 3/6] tracing: add trace_export support for event trace Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 4/6] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 5/6] stm class: ftrace: enable supported trace export flag Tingwei Zhang
2020-07-28  1:33 ` [PATCH v3 6/6] stm class: ftrace: use different channel accroding to CPU Tingwei Zhang
2020-08-11  3:04 ` [PATCH v3 0/6] tracing: export event trace and trace_marker 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 [this message]
2020-08-11  3:57 Tingwei Zhang
2020-08-12 16:49 ` Mathieu Poirier
2020-08-13  1:47   ` Tingwei Zhang
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-09-03  0:17 Tingwei Zhang
2020-09-14 23:27 ` Tingwei Zhang
2020-09-18 14:26   ` Alexander Shishkin

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=20200811064529.GA4253@codeaurora.org \
    --to=tingweiz@codeaurora.org \
    --cc=jinlmao@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=saiprakash.ranjan@codeaurora.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tingwei@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;
as well as URLs for NNTP newsgroup(s).