On Tue, Aug 11, 2020 at 12:03:33PM +0800, Steven Rostedt wrote: > On Tue, 11 Aug 2020 11:49:46 +0800 > Tingwei Zhang <tingw...@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 <tingw...@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
