linux-kernel - Re: [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2

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-=wg5_Hu4W5tz05vmC3eBH3_h7_uJKEMwLM+MvsJ=znWtbw@mail.gmail.com>
Date:   Tue, 26 Mar 2019 14:29:27 -0700
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/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2

On Tue, Mar 26, 2019 at 11:48 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Should I work on changing this?

I don't personally much care, but the pr-tracker-bot clearly does.

If you don't care about the automated "it's been pulled" message, that
doesn't matter, of course.

That said, I'd almost prefer to get just the regular pull request
without the patches. If the complete patch is small, it's often nice
to see that _in_ the pull request (at the bottom), but I don't
generally need or want the individual patches themselves as separate
emails (unless there's some particular reason you want me to comment
on something, or apply them directly as patches).

                   Linus