Message-ID: <1457535868.28618.6.camel@tzanussi-mobl.amr.corp.intel.com>
Subject: Re: [PATCH 00/23] tracing: 'hist' triggers
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: masami.hiramatsu.pt@hitachi.com, namhyung@kernel.org,
        josh@joshtriplett.org, andi@firstfloor.org,
        mathieu.desnoyers@efficios.com, peterz@infradead.org,
        linux-kernel@vger.kernel.org
Date: Wed, 09 Mar 2016 09:04:28 -0600
In-Reply-To: <20160309094424.613668a7@gandalf.local.home>
References: <cover.1457029949.git.tom.zanussi@linux.intel.com>
	 <20160309094424.613668a7@gandalf.local.home>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1414
Lines: 46

Hi Steve,

On Wed, 2016-03-09 at 09:44 -0500, Steven Rostedt wrote:
> On Thu,  3 Mar 2016 12:54:40 -0600
> Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> 
> > This is v16 of the 'hist triggers' patchset.
> > 
> > This version incorporates a couple changes suggested by Steve.
> > 
> > Patch 1 can be merged into patch 8 from v13, 'tracing: Add lock-free
> > tracing_map'.  Following the v13 suggestions, I made a couple changes
> > to the tracing map constants to clarify the field relationships, and
> > added a couple missing comments I noticed while at it.
> > 
> 
> Hi Tom!
> 
> I tested this, played with it a little, and I think it's pretty much
> ready to go. But I'm very nervous about sending this to Linux-next this
> late in the current rc cycle. I would like this in next for a full
> cycle before sending it to Linus.
> 
> Thus, I'm going to push everything up to but excluding:
> 
>   tracing: Add lock-free tracing_map
> 
> The hist tree that I tested and played with is on my repo in
> ftrace/hist branch.
> 
> I'll push this to linux-next after 4.6-rc1 is released, and then we can
> get it into the 4.7 merge window.
> 
> Does that sound fine to you?
> 

Yeah, it's been kicking around for a couple years now, so one more cycle
won't hurt. ;-)  (and I do think it having it soak in linux-next for a
full cycle makes a lot of sense).

Thanks for all your review and testing!

Tom

> -- Steve