linux-kernel - Re: [PATCH/RFC] tracing: make trace_marker{,

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] [day] [month] [year] [list]

Message-ID: <20211207090347.15822d87@gandalf.local.home>
Date:   Tue, 7 Dec 2021 09:03:47 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     John Keeping <john@...anate.com>
Cc:     linux-trace-devel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH/RFC] tracing: make trace_marker{,_raw} stream-like

On Tue, 7 Dec 2021 10:31:15 +0000
John Keeping <john@...anate.com> wrote:

> Were you expecting more input from me on this?  The above sounded like
> "will be added for 5.16" but I don't see this change in v5.16-rc4 and
> the patch is still marked as "New" in patchwork [1]
> 
> [1] https://patchwork.kernel.org/project/linux-trace-devel/patch/20210909115734.3818711-1-john@metanate.com/

And that explains why I didn't add it :-(

The linux-trace-devel is mainly for user space tools, although some kernel
patches end up there too. Any patch that hits my inbox without Cc'ing
linux-trace-devel falls into my internal patchwork. I look at that one
first for kernel patches to add to my queue, and then I'll look at that
public one. I forgot about this conversation, and because the title of that
patch has RFC in it, I thought there would be another patch coming. I don't
add RFC patches generally, and forgot about this conversation.

Can you resend the patch to me, but remove the linux-trace-devel mailing
list (but still include linux-kernel).

Thanks!

-- Steve