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+55aFzuOAn4d4gkvXNAfNnRwgsAa3G4H9HJNUfSxDJ0Wetagw@mail.gmail.com>
Date:   Mon, 26 Feb 2018 08:13:09 -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] KVM changes for 4.16-rc3

On Mon, Feb 26, 2018 at 12:28 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> I rebased to correct a "Fixes" tag that pointed to the wrong commit.
> This: https://marc.info/?l=kvm&m=151943277910352&w=2 is the mail that
> pointed out the right commit, and you can see that those 28 commits have
> times that are clustered five minutes after that mail.
>
> The SEV patches indeed have been committed about half an hour before
> sending the PULL request, because no one outside AMD has all the
> hardware and code to test them.  Half an hour is about the time it takes
> me to do the final smoke test before sending a pull request.

So this is the kind of information I'd like to see in the pull
request, so that I don't have to wonder why something went wrong.

I'll pull again after I've had my morning coffee.

              Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ