linux-kernel - Re: [GIT PULL] First batch of KVM changes for 4.2

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: <558ADCE3.5090200@redhat.com>
Date:	Wed, 24 Jun 2015 18:37:55 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Gleb Natapov <gleb@...nel.org>, KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for 4.2



On 24/06/2015 18:33, Linus Torvalds wrote:
> On Tue, Jun 23, 2015 at 9:49 AM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>> >
>> > There are some x86 conflicts, one with the rc8 pull request and
>> > the rest with Ingo's FPU rework.
> Hmm. I'm dropping the "fx_init(..init_state)" changes from you pull
> request, since fx_init is static and only has one caller, and that one
> had init_state being false.
> 
> Was there something I missed? That was true even in your tree,
> regardless of Ingo's FPU changes?

No, you didn't.  There was some problem in the rest of the series that
introduced init_state, and the unused parameter remained.

> If you will grow a second user with init_state set to "true", you'll
> have to re-do your patch.

No problem.

Thanks!

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/