[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1533826297.1918.2.camel@kernel.org>
Date: Thu, 09 Aug 2018 09:51:37 -0500
From: Tom Zanussi <zanussi@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
vedang.patel@...el.com, bigeasy@...utronix.de,
joel@...lfernandes.org, mathieu.desnoyers@...icios.com,
julia@...com, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v3 0/7] tracing: Hist trigger snapshot and onchange
additions
Hi Steve,
On Thu, 2018-08-09 at 10:47 -0400, Steven Rostedt wrote:
> On Thu, 9 Aug 2018 09:34:10 -0500
> Tom Zanussi <zanussi@...nel.org> wrote:
>
> > From: Tom Zanussi <tom.zanussi@...ux.intel.com>
> >
> > Hi,
> >
> > This is v3 of the hist trigger snapshot and onchange additions
> > patchset. It's rebased on top of the latest ftrace/core and adds a
> > few fixes to some handler/action problems I noticed while testing.
>
> Hi Tom,
>
> How ready is this? I'm still dealing with the fallout of the preempt
> irqs tracepoint updates, and trying to get that stable before pushing
> to linux-next. Are you confident that these are solid enough to pull
> in
> this late before the merge window opens? Or should I ignore them
> until
> the merge window closes and push this for the following release?
>
I wasn't really expecting they'd go into this merge window, so no
problem ignoring them until the next release..
Thanks,
Tom
Powered by blists - more mailing lists