linux-kernel - Re: [PATCH v4 06/12] tracing: Change trace_boot to use synth

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: <20200131130020.51d04203@gandalf.local.home>
Date:   Fri, 31 Jan 2020 13:00:20 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Tom Zanussi <tzanussi@...il.com>
Cc:     artem.bityutskiy@...ux.intel.com, mhiramat@...nel.org,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v4 06/12] tracing: Change trace_boot to use synth_event
 interface

On Fri, 31 Jan 2020 12:55:39 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Fri, 31 Jan 2020 11:49:01 -0600
> Tom Zanussi <tzanussi@...il.com> wrote:
> 
> > Hi Steve,
> > 
> > It looks like you missed this patch when you pulled the other ones into
> >  for-next.
> >   
> 
> Ah, you're right! And my INBOX patchwork is informing me of it too (I
> have it read my email, and when I post the 'for-next' patches, it
> switches the status from "new" to "Under review", and this one is still
> "new").
> 
> Thanks for letting me know. I'll apply it now.

My latest has been pushed to ftrace/core.

-- Steve