linux-kernel - Re: [PATCH v2] kvm: Use pci_enable_msix_exact() instead of pci_enable

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <5307C6D9.4030503@redhat.com>
Date:	Fri, 21 Feb 2014 22:36:25 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Alexander Gordeev <agordeev@...hat.com>
CC:	linux-kernel@...r.kernel.org, Gleb Natapov <gleb@...nel.org>,
	kvm@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH v2] kvm: Use pci_enable_msix_exact() instead of pci_enable_msix()

Il 21/02/2014 19:56, Alexander Gordeev ha scritto:
> On Fri, Feb 21, 2014 at 06:11:29PM +0100, Paolo Bonzini wrote:
>> It's okay, but it's not clear to me whether I should include this
>> patch or someone else will. :)
>
> Please, include it.

And where do I get pci_enable_msix_exact?  When will pci_enable_msix 
disappear?

So, do I have to pull something (which I'd rather not, since pulling the 
wrong thing in a submaintainer tree will make Linus angry), or should I 
do it in the next merge window after pci_enable_msix_exact gets in?

All in all, it seems much simpler to me if the linux-pci tree just 
includes the whole patch series with my Acked-by.

Paolo

> 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/