linux-kernel - Re: [GIT PULL] First batch of KVM changes for 5.6 merge window

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:   Fri, 31 Jan 2020 22:27:25 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Borislav Petkov <bp@...e.de>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Sean Christopherson <sean.j.christopherson@...el.com>,
        Xiaoyao Li <xiaoyao.li@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for 5.6 merge window

On 31/01/20 22:24, Borislav Petkov wrote:
>> I was supposed to get a topic branch and fix everything up so that both
>> CPU_BASED_ and VMX_FEATURE_ constants would get the new naming.  When
>> Boris alerted me of the conflict and I said "thanks I'll sort it out",
>> he probably interpreted it as me not needing the topic branch anymore.
>> I then forgot to remind him, and here we are.
>
> Damn, that was a misunderstanding. I actually had a topic branch:
> tip:x86/cpu and was assuming that you'll see it from the tip-bot
> notifications. But they went to lkml and you weren't CCed. And
> regardless, I should've told you explicitly which one it is, sorry about
> that. I'll be more explicit next time.

No problem, it's fair to say that we both did our best to mess this up. :)

Paolo