linux-kernel - Re: [PATCH v3 0/7] tracing: Hist trigger snapshot and onchange additions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1533826609.1918.3.camel@kernel.org>
Date:   Thu, 09 Aug 2018 09:56:49 -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

On Thu, 2018-08-09 at 10:55 -0400, Steven Rostedt wrote:
> On Thu, 09 Aug 2018 09:51:37 -0500
> Tom Zanussi <zanussi@...nel.org> wrote:
> 
> > 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..
> > 
> 
> Great, that makes things easier. Can you ping me after the merge
> window
> closes to remind me to take a look at these? Much appreciated if you
> do :-)
> 

Sure, will do!

Tom