Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1525432

Re: [PATCH V8 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only

Show all headers | View raw

Steven Rostedt <rostedt@goodmis.org> writes:

> This looks good to me, although I would like this to go through my tree
> (to make sure it gets all my testing). I understand the next two
> patches depend on this, how would you want to go about that?
>
> One is that I can pull it in the next merge window, and the rest go in
> after that. Or I can take the other two patches with the proper acks as
> well.

I just asked for the last patch be split 4 ways, but otherwise, they
have my acks. If Chunyan can do that, you can take all of them into your
tree.

Thanks,
--
Alex

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH V8 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only Chunyan Zhang <zhang.chunyan@linaro.org> - 2016-11-18 04:10 +0100
  Re: [PATCH V8 1/3] tracing: add a possibility of exporting function  trace to other places instead of ring buffer only Steven Rostedt <rostedt@goodmis.org> - 2016-11-18 15:30 +0100
    Re: [PATCH V8 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-11-18 16:00 +0100
      Re: [PATCH V8 1/3] tracing: add a possibility of exporting function  trace to other places instead of ring buffer only Steven Rostedt <rostedt@goodmis.org> - 2016-11-18 17:50 +0100
        Re: [PATCH V8 1/3] tracing: add a possibility of exporting function  trace to other places instead of ring buffer only Chunyan Zhang <zhang.chunyan@linaro.org> - 2016-11-21 04:20 +0100

csiph-web