linux-kernel - Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

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]

Date:   Wed, 31 Oct 2018 05:36:36 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>, mhiramat@...nel.org
Subject: Re: [GIT PULL] tracing: Updates for 4.20 (or 5.0)

On Tue, 30 Oct 2018 10:02:16 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> As an explanation, the above kind of sucks. "SDT"? I had to look it
> up. I added a note to the commit message, but please, don't use random
> acronyms in kernel explanations unless they are industry-standard and
> comprehensible to kernel people.
> 
> Good acronyms: "TLB", "WTF", "LOL". People know what those mean.
> "SDT"? Not so much.

Apologies, this is one of the reasons I wanted to wait till the end of
the week to do the pull request. I'm currently traveling (on my way
home), and using my laptop for all my work (at home I use my
workstation). I almost sent the pull request without even mentioning
the SDT work. That's because I had tested that and pushed it into
linux-next some time ago and completely forgot about it. I caught the
error looking at the patches before sending, redid the signed tag by
mentioning it and sent it out.

I would have had a deeper explanation about the change otherwise. I
really hate merge windows while I'm traveling :-(

-- Steve