linux-kernel - Re: [PATCH V2 0/9] rtla improvements

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: <20230529044307.2dcfca3d@rorschach.local.home>
Date:   Mon, 29 May 2023 04:43:07 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Daniel Bristot de Oliveira <bristot@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-trace-devel@...r.kernel.org,
        linux-doc@...r.kernel.org, Juri Lelli <juri.lelli@...hat.com>,
        William White <chwhite@...hat.com>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH V2 0/9] rtla improvements

On Mon, 29 May 2023 10:38:16 +0200
Daniel Bristot de Oliveira <bristot@...nel.org> wrote:

> On 5/29/23 10:28, Steven Rostedt wrote:
> > Hi Daniel,
> > 
> > Could you make sure to Cc linux-trace-kernel@...r.kernel.org and not
> > linux-trace-devel. The former is for any patch that goes into the
> > kernel repo, the later is for the tracing libraries (like libtracefs).
> > The reason why this matters is that the patchwork that is associated to
> > the Linux kernel tree will not get these (and I will not work on them
> > when I'm working on kernel patches). But it will go into the 
> > patchwork for the libraries (and never be processed by the patchwork
> > infrastructure), and I will likely not work on them, because when I
> > look at the library patchwork, I ignore anything that goes into the
> > kernel.  
> 
> Sure, I will do that. IIRC, we agreed that we would use linux-trace-devel for
> rtla because it is a user-space tool. But I agree with you, as they are patches
> going to the kernel repo, linux-trace-kernel is a better place. It is easier to
> myself too... :-).

I think we agreed on that because linux-trace-kernel didn't exist yet ;-)

> 
> > 
> > Perhaps resend with the proper Cc and it will then be processed. I
> > allowed this to happen before, but that's because I did everything
> > manually and not with my scripts. And I'm tired of doing that.  
> 
> I will do that in the v3.
> 
> I will also update the maintainers entry for RTLA and RV, as both are pointing to
> linux-trace-devel.

I already sent the patch!

-- Steve