linux-kernel - Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

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+55aFzMwgatwF=sudndpPs3YMfgY89s76pLO6VF1z-1ZqufcA@mail.gmail.com>
Date:   Mon, 27 Nov 2017 11:16:51 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Radim Krčmář <rkrcmar@...hat.com>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

On Mon, Nov 27, 2017 at 2:35 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> They came from the submaintainers' tree, so technically it wasn't in *my*
> linux-next tree; if you looked at "linux-next as of the kvm/linux-next merge",
> you wouldn't have found them.  But they were not rebased at least between
> 20171113 and 20171117:

I don't look into specific branches, I looked just at the status at 20171117.

Basically I do a fetch of the requested branch, and then check what is
in the fetch that wasn't in next-20171117. There was a lot there,
which is why I complained.

                  Linus