linux-kernel - Re: [GIT PULL] printk for 4.17

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: <CA+55aFyukB0HkH+58ssWeEL-xBbcpwO1mcfYoPEO0gPPEXQjtg@mail.gmail.com>
Date:   Thu, 5 Apr 2018 19:56:04 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Petr Mladek <pmladek@...e.com>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] printk for 4.17

On Wed, Apr 4, 2018 at 5:39 AM, Petr Mladek <pmladek@...e.com> wrote:
>
> Petr Mladek (1):
>       Merge branch 'for-4.17' into for-linus

Please don't do this.

There was no reason for it, and the commit message says:

  "Merge branch 'for-4.17' into for-linus"

which also doesn't tell why that merge would have existed.

You should just have asked me to pull "for-4.17". Or renamed the
branch to "for-linus". There was no reason for the merge that I can
see.

So what I actually did was to just pull your 'for-4.17' branch
instead, which got me the exact same end result.

                   Linus