linux-kernel - Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

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: <CAHk-=wgJErbyjbAy=cFHUcT7STP7taGtTBX5sfAgkTX6Yq6Skg@mail.gmail.com>
Date:   Fri, 30 Nov 2018 10:56:06 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: More fixes for 4.20

On Fri, Nov 30, 2018 at 9:41 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I went back and merged things [..]

Note that I did this as two merges, even if one would have done (since
the second pull request was just adding new commits on top of the
first).

This way I got the matching diffstat from your pull requests, but more
importantly also the independent merge messages.

The history looks slightly odd this way (with two adjacent merges of
continuous history), but I thought I'd explain the reason.

                   Linus